💾 Archived View for station.martinrue.com › jmcs › 72dd1fb52e744d5f96473792fa946410 captured on 2024-12-17 at 14:55:59. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
open question: is the "standard" to only use "ANSI color codes" inside "preformatted text"? it seems to be the norm, but...
Anyone has input?
thanks!
5 days ago · 👍 io_cat
I haven’t read the entire spec, but I don’t think ANSI is part of the gemtext standard (though some clients may choose to implement such a feature).
If it is in the standard then there should be information on it at the following URLs:
gemini://geminiprotocol.net/docs/gemtext-specification.gmi
gemini://geminiprotocol.net/docs/gemtext.gmi · 21 hours ago
gemini://geminiprotocol.net/docs/gemtext-specification.gmi
gemini://geminiprotocol.net/docs/gemtext.gmi
I'm asking because I'm trying to add ANSI color text support to Deedum (it's not going bad, there are libraries out there for everything...). So far, I have only seen notes about this topic on Lagrange's Readme 😃.
So, yeah, I guess we'll have to accept that the convention is to have "color" only on "pre" texts. · 4 days ago
I don't think this is a standard even — if only an unwritten one. I think at some point I've even seen a discussion somewhere about whether this behaviour should be standardised and no agreement was reached — because it complicates the bottomline Gemini client implementation. So AFAIK it's just an experiment in Lagrange, but as Lagrange became a de-facto standard, some clients might just follow suite 🤷 · 4 days ago
Yes. This is because graphical clients wouldn’t know what to do with the escape codes. It would also make the life of screen readers hell. Terminal based Gemini clients would probably render it fine but it would break everywhere else. Preformatted text blocks, however, are often rendered with “terminal emulation” in eg. Lagrange so it still works. · 5 days ago