💾 Archived View for gemi.dev › gemini-mailing-list › 000363.gmi captured on 2024-08-31 at 16:48:28. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Language tags in Luke's "A proposed scheme for parsing preformatted alt text"

1. Nathan Galt (mailinglists (a) ngalt.com)

📅 Sent: 2020-09-07 18:27
📧 Message 1 of 1

Prior reading:

gemini://gemini.marmaladefoo.com/blog/7-Sep-2020_Parsing_preformatted_alt_t
ext.gmi                                                  

I haven?t made up my mind on, well, most things in this proposal. I?m 
still chewing on them, and I may never have an opinion on them, much less 
a well-thought-out opinion.

That said, I think that if we?re writing language codes in text, we ought 
to allow for full IETF language tags instead of just two-letter codes, 
although roughly nobody?ll bother writing any more than ?lang:en-GB?. I 
might do `lang:en-Shaw` once or twice, but that?s about it.

https://en.wikipedia.org/wiki/IETF_language_tag

That way, if people want to express more than just a language, there?s a 
well-trodden path for them to do so. Likewise, if, say, a screen reader 
wants to pick the right accent for a particular bit of text, it can.

Nathan

Link to individual message.

---

Previous Thread: Labyrinth II

Next Thread: Unadorned Gemtext instead of syndication formats