Proposed minor spec changes, for comment.

[epoch]

On Tue, May 19, 2020 at 09:21:13AM +0000, defdefred wrote:
> On Tuesday 19 May 2020 02:07, Sean Conner <sean at conman.org> wrote:
> 
> > I thought about autodetection---Unicode is defined in blocks, where each
> > alphabet becomes a defined block in Unicode. I then realized that there are
> > multiple languages that use the European block. Sure, detecting Greek is
> > easy since they have their own alphabet, but what about Spanish, French and
> > German? They use the same alphabet.
> 
> Autodetection is necessary for document using multiple languages.
> Browser preference is fine for hard to detect case.
> 

I was thinking, maybe add a "lang" parameter to the end of mime-types, like how charset and boundary work.

Then, if people want multiple languages per-"document"? I guess per-response. They can use
mime multipart, then when the mime-type for each part is picked, they can put the language there.

That doesn't really help with "inline" different languages. Example gemini response:

20 multipart/mixed; boundary=longrandomthing
--longrandomthing
Content-Type: text/plain; lang=en-US

color. withOUT a 'u'. ha.
--longrandomthing
Content-Type: text/plain; lang=jp

[insert some japanese here]
--longrandomthing--


This document seems like it might come in handy:

https://www.w3.org/International/articles/language-tags/