4 ms·
You don't need to be so accusatory or ungenerous about it. Clearly "anglosphere programmers" fathom it every day when they use UTF-8 almost universally in webp
by crazygringo 5y ago
You don't need to be so accusatory or ungenerous about it.
Clearly "anglosphere programmers" fathom it every day when they use UTF-8 almost universally in webpages. Also, you know, things like emoji are pretty popular in the "anglosphere" as well.
It's obvious that the real reason is an ancient e-mail RFC, and that while upgrading webpages to UTF-8 was relatively easy, in that it only needs 2 parties to support it -- the browser and the server -- upgrading e-mail is almost infinitely more complicated, because you have to wait for virtually all email code in the world to be upgraded, since an e-mail address is pretty useless if it doesn't work everywhere.
It other words, it's a coordination problem. Not an ignorance problem.
And unfortunately, Punycode [1] doesn't seem to be a particularly viable stepping-stone/compatibility solution here. E.g. if a user tries to use ドメイン名例@example.com and it fails, asking them to instead type in a seemingly-gibberish eckwd4c7cu47r2wf@example.com, where that could also conflict with a real e-mail address of that name.
[1] https://en.wikipedia.org/wiki/Punycode https://en.wikipedia.org/wiki/Punycode
- Avamander 5y ago> You don't need to be so accusatory or ungenerous about it. At least four decades of mostly bad internationalization support it's no longer accusatory, it's empirical and quite generously worded.