💾 Archived View for rawtext.club › ~sloum › geminilist › 004719.gmi captured on 2023-12-28 at 16:41:56. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
CĂ´me Chilliet come at chilliet.eu
Mon Jan 4 09:28:08 GMT 2021
- - - - - - - - - - - - - - - - - - -
Le dimanche 3 janvier 2021, 17:13:10 CET Petite Abeille a Ă©crit :
On Jan 3, 2021, at 17:11, CĂ´me Chilliet <come at chilliet.eu> wrote:
No, the specification specifies that default is utf-8, so unspecified is utf-8.
Precisely my point. Thanks.
No, you said «Not quite.» when Stephane said UTF-8 had quasi-monopoly, and you rectified «Unspecified rules».Unspecified is UTF-8, by specification. So UTF-8 does have a quasi-monopoly.
No one said it was the same. But it would be interesting to know.
The fact that you made a difference between unspecified and utf-8 for encoding, and that you provided both tools to detect encoding and language made it seem like you were considering both cases the same, while encoding is always known (unspecified == utf-8) while language is sometimes unknown.I also explicitely pointed this difference to encourage people to specify the language in their Gemini headers, as a lot of Gemini pages currently have an unspecified language.
What's your server? We can validate that promptly.
Please stop splitting your answers in several emails like this, it’s uselessly filling the mailing list and making discussions harder to follow.I do not need to validate that, I know that my server header does not contain a charset tag.
CĂ´me