Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse the Resource Description Chunk #50

Open
curiousdannii opened this issue Feb 10, 2024 · 3 comments
Open

Parse the Resource Description Chunk #50

curiousdannii opened this issue Feb 10, 2024 · 3 comments

Comments

@curiousdannii
Copy link
Contributor

I only just noticed, but it looks like gi_blorb.c doesn't use the RDes chunk.

@erkyrath
Copy link
Owner

erkyrath commented Jul 11, 2024

Hm... (Reviewing what the heck was going on here...)

One way to wire all this together is for GlkOte to have a resource map already set up, with URLs and alt texts ready to go. Then RemGlk just sends over image numbers and GlkOte handles the rest.

Of course RemGlk can send URLs (that's the point of the -resourceurl argument). In that case, it ought to send alt texts as well. And it might not be GlkOte on the other end -- that's where you came in, I imagine.

I see there's a field defined in giblorb_auxpict_t (gi_blorb.c) to hold the alttext, and an incomplete bit of code in data_specialspan_print() which could send it out.

@curiousdannii
Copy link
Contributor Author

I'd just been going off the GlkOte docs, where the alttext is part of the protocol. https://eblong.com/zarf/glk/glkote/docs.html#imagedata

TBH I don't really mind what you do here now as I've basically switched to my RemGlk port.

@erkyrath
Copy link
Owner

Ok. I suspect the protocol doc should be clearer about what fields are optional and when.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants