💾 Archived View for rawtext.club › ~sloum › geminilist › 001426.gmi captured on 2020-10-31 at 02:16:15. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
int 80h int at 80h.dev
Mon Jun 8 18:10:42 BST 2020
- - - - - - - - - - - - - - - - - - -
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 itcould 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 ofit 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 theresponse header.
int 80h