https://mediaoptions.com/blog/understanding-numeric-domain-v...
But of course giving websites control over the display of their domain name is a major security headache. No idea what kind of stuff would be possible and how it would interact with TLS.
What happens when someone registers θεν.com and someone else gets δεν.com, since both transliterate into ASCII as then.com?
In short, the idea has many potential pitfalls.
capitalization: HarryPotter.Hogwarts.UK
Of course we'd have a lot of lookalike domain problems, like we have with IDN now (:
If you can't type 你好.com you're simply not the website's intended audience.
Imagine being forced to only register 1337-code domains because some other country doesn't have Latin key caps on their keyboards.
Not understanding the local writing system or language does suck for foreigners, but most people in the world aren't foreigners in the country they live in.
Why should countries almost exclusively using the Arabic script be forced to switch between Latin and their normal way of writing because they want to edit the URL between writing comments? Why shouldn't people native in the 120+ languages using Devanagari be able to register domains?
Pragmatically speaking, the lack of proper language support in many non-Latin websites had led to a significant amount of them using images for labels rather than text, making Google/Bing/Baidu Translate worthless for navigating them. If you know what 你好.com is supposed to provide or sell to you, you can find it in a search engine and manually picture-check the domain if you want to be sure; the burden of being available to people outside your target demographic shouldn't fall on you just because a tiny slither of your user base doesn't understand your writing system, but you can opt into making it easier for them to find your website regardless.
It's normal to expect technology to evolve to be usuable by all rather than expect people changing to conform to technology. People should fight for that more often.
It may be debated that with introduction of punycode, support for real accent and non ASCII characters was hindered.
https://pi.cr.yp.to/ experimented with UTF-8 in domain names before punycode and this will rarely ever work in the future, purely because now we have a half-solved problem with punycode and no one will bother to implement UTF-8 domains - it's would be ambiguous.
I'm not picking a side; you just seem to have supremely misinterpreted their position.
The standards do have limitations anyway. For instance, you cannot have an underscore in a hostname on the internet. You can have one in a CNAME, technically, but most CAs will not sign a certificate for any name with an underscore.
It's weird that Google prefers the IDN variant under national TLD instead of the non-IDN variant with an IDN counterpart under .eu.
Another interesting phenomenon is that chromium detects suspicious activity and informs the user if he meant to go to š.tld when visiting s.tld. Or vice-versa, depending on which site he opened first I think. It's nice how the browser detects different ownership - this does not happen for other TLDs where I own both domains.