On Mon, May 18, 2020 at 09:45:35PM +0000, jan6 at tilde.ninja wrote: > I'm not sure I see the point in the encoding part, though... > practically everything can be converted to utf8 rather easily, making it a bit useless to > specify... That's been in the spec since early days, the only proposed change here is the language part. The charset parameter is explicitly optional and the default in its absence is UTF-8, which clients MUST support. Support for additional encodings in clients is optional, but they should fail gracefully in the face of things they can't handle. I expect 90%+ of content to be UTF-8 and for servers not to bother specifying this as it's the explicit default, but it seemed unwise to be completely incapable of handing anything else. Cheers, Solderpunk
---
Previous in thread (17 of 63): 🗣️ colecmac (a) protonmail.com (colecmac (a) protonmail.com)
Next in thread (19 of 63): 🗣️ solderpunk (solderpunk (a) SDF.ORG)