Three month spec freeze

[James Tomasino]

On 6/3/20 11:40 AM, Felix Queißner wrote:
> So, what you are saying is:
> Most people already use utf-8, so there's no reason to enforce utf-8?
> 
> I think it's even more an argument to enforce UTF-8. It makes the
> software way simpler and less error pronce, reducing the possibilities
> of attacks via badly implemented encodings and also reduces the risk of
> il-translated and badly displayed text.
> 
> Why drag a dependency on old cruft in when Gemini wants to be "as slim
> as possible" and does not need to take care of "the old problems".

I didn't have much skin in this discussion at the start, but the more I
understand things the more I support enforcing UTF-8 in text/gemini.

To be clear, though, we're talking specifically about text/gemini,
right? Not text/*. Since text/gemini support is all that's minimally
required for a client then only UTF-8 is minimally required for that
format. If authors were to add support for wider mime types they could
also add support for other encodings there. Or am I not following along
properly?