IETF policy on encodings and languages

[Arav K.]

On Mon, Dec 28, 2020 at 11:45:56AM +0100, Petite Abeille wrote:
> Yes, but this doesn't help with 1x responses. They are meant to be
> presented to the end user, as a prompt. And they lack a language tag.
> This is my understanding of the crux of the issue. But perhaps I
> missed something.

My point was that the client is communicating the language the server
should use in the URL itself, e.g. for gemini://fr.example.com/search
the server would send a prompt in French.  If no language is specified,
the server should assume a default language, which would often be
English.

I thought this didn't need to be mentioned, but if the server supports
the URL gemini://fr.example.com/, then it is expected to have a French
interface for it.  If it doesn't support a language, then it just
shouldn't offer it, and it then becomes the user's responsibility to
translate appropriately.

~aravk | ~nothien
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201228/2d3e964f/attachment.sig>