Quote:
|
Originally Posted by mole Yeah, IDN's are more local friendy, but to do that they will have to tear apart the very fabric of what makes the Internet so universally convergent. Hindi, Thai, Arabic, Modern Chinese, Traditional Chinese and hundreds of other streams too long to mention.
Imagine the hundreds of thousands of sysads around the world trying to figure how to set up their email servers for this, let alone browsers on user computers, and the countless security issues that will arise because of configuration boo boos.
Unicode is there for a reason - not the best reason, but there is a reason.
I'm all for new namespace, but 한글.kr 日本語.jp مصريين.com 中国互联网络信息中心.cn đäňîċ-ţÃ¥ŝŧďómãĵņ.de is pushing flexibility a bit much.
Might as well go buy some New.Net domains. |
Mole,
These domains are already up and functioning and not causing any real distress to the DNS.
All IDN characters are Unicode. It is ASCII that the DNS requires and the IDNs are encoded into the basic ASCII character set. That's the whole point.
This is only a temporary glicht. Unfortunately, the criminal fraternity seem to have much more imagination than the rest of the world.
Firefox and Thunderbird had made the need to set up anything clever absolutely unnecessary. Far better than IE which kept telling me sites were down when they weren't. Presumably in Firefox 1.1, all that will happen is there will be a little routine than pops up a warning message to tell you that you are entering an IDN site, until such time as you choose to switch it off.
I started collecting IDN when disillusioned with the high prices for dot com drops, and the general lack of interest in my dot net investments. I agree with you, however, that with the change in the dot net contract, there will be a lot of interest this year.
Regards
Dave Wrixon
Regards
Dave Wrixon