On Mon Jun 8, 2020 at 3:36 AM EDT, solderpunk wrote: > No, the "lang" parameter is a parameter to the text/gemini MIME type > which is part of the response header. It doesn't go in the document > itself. Server software will need to provide admins and/or users some > way to configure this. The way I was thinking is have the server look at the first line for "#lang" then strip it and put it in the response header. That way it could be an implementation of the server and not the spec itself. > Multi-lingual sites would probably work best with content in different > languages separated by the path hierarchy, and servers could let people > designate different languages depending on which regex the path matches. > > Multi-user sites will be trickiest of all and will require users to > either bother the admin, or for servers to implement something like > Apache's .htaccess files. Something like .htaccess could work. This morning I was also thinking of it being in the file name. Then it could be on a per file basis like "index.fr.gmi" would be sent as "index.gmi" with "lang=fr" in the response header. int 80h
---
Previous in thread (21 of 35): 🗣️ Matthew Graybosch (hello (a) matthewgraybosch.com)
Next in thread (23 of 35): 🗣️ solderpunk (solderpunk (a) SDF.ORG)