IETF policy on encodings and languages

[Petite Abeille]

> On Dec 28, 2020, at 11:57, Arav K. <nothien at uber.space> wrote:
> 
> 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.

Sounds reasonable enough to me: language tags are conveyed through the expedient of embedding them in the user generated content, i.e. the URL, by convention. And not the protocol machinery, i.e. status codes, as per the specification.

I thought that John's point of contention was the protocol machinery, as opposed to the user generated content.