As stated by the W3C, the charset parameter can be set to "any character encoding that has been registered with IANA". A full list of these is available on their website.
Notably missing from that list is the utf8 value that was being used for email charsets. The strictly more correct name is utf-8 (or UTF-8, since these names are case-insensitive).
The popularity of UTF-8 has meant that aliases like utf8 are supported by a number of email servers. Unfortunately, not all are as accommodating (see for example https://github.com/emersion/hydroxide/issues/165), so a more standard name means Synapse can be used even with the more opinionated servers.
Pull Request Checklist
[x] Pull request is based on the develop branch
[x] Pull request includes a changelog file. The entry should:
Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from EventStore to EventWorkerStore.".
Use markdown where necessary, mostly for code blocks.
End with either a period (.) or an exclamation mark (!).
Start with a capital letter.
Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry.
clokep
commented
1 year ago
As stated by the W3C, the charset parameter can be set to "any character encoding that has been registered with IANA". A full list of these is available on their website.
Notably missing from that list is the
utf8value that was being used for email charsets. The strictly more correct name isutf-8(orUTF-8, since these names are case-insensitive).The popularity of UTF-8 has meant that aliases like
utf8are supported by a number of email servers. Unfortunately, not all are as accommodating (see for example https://github.com/emersion/hydroxide/issues/165), so a more standard name means Synapse can be used even with the more opinionated servers.Pull Request Checklist
EventStoretoEventWorkerStore.".code blocks.