IETF policy on encodings and languages

[Étienne Deparis]

lun. 28 déc. 2020 à 03:04, cowan at ccil.org a écrit :

> On Sun, Dec 27, 2020 at 6:04 PM Petite Abeille <petite.abeille at gmail.com>
> wrote:
>
> Now that I think about it, though, that *can* be encoded in the URL readily
> enough, though not in a universal way If a text/gemini file is in Greek,
> the textual part of a link line will also normally be Greek, in which case
> the URL should have "gr" in it someplace (assuming the server can handle
> it).

I have a similar thought: I think we should somehow avoid too generic
input. I mean, when the user is prompted by an input, it’s normally
after having click on some link. Thus maybe we should think
differently. For an internalized website, it’s easy to imagine different
section, each one for different language. And thus each of these pages
will be on a different specific language, maybe reflected in their
URL. Then, it’s up to the CGIs running the site to be able, for a
similar function, to serve an input request with the correct language,
following the page where the user was when they click (again, obviously
because of some difference in the URL).

Said otherwise, we should maybe avoid to think too much on a specific
problem, and think it again as part of a much broader situation, with
easier solutions around the corner.

--
Étienne Deparis

gemini://alltext.umaneti.net/
xmpp: etienne at depar.is