Statement of intent regarding document encodings
Drew DeVault
sir at cmpwn.com
Tue Nov 10 16:47:07 GMT 2020
I am stopping by to clarify another intepretation of the Gemini spec
made by my implementations.
https://git.sr.ht/~sircmpwn/gmni
https://git.sr.ht/~sircmpwn/kineto
With respect to the charset parameter of the document mimetype for
text/gemini documents, it is our intention to ONLY support UTF-8, and to
raise an error if any other content encoding is specified.
We won't refuse other text/* documents with an arbitrary encoding,
though we won't display them - we'll just let the user download them.
All text/gemini documents are new, and can be expected to be written in
a sane text encoding. Other text documents may use other encodings for
historical reasons, and therefore will not be refused outright.
It's 2020, and I have a zero tolerance policy for dumb encodings.
More information about the Gemini
mailing list