,by Michael S. Kaplan, published on 2012/08/08 08:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2012/08/08/10337799.aspx
Previous blogs in this series:
I knew at some point I'd have to deconstruct the support of International Domain Names in Internet Explorer.
In other words, IDN in IE. :-)
Unfortunately, it is pretty complicated.
So I was looking forward to it like I'd look forward to a root canal, you know?
Thankfully, Eric Lawrence saved me the trouble!
In EricLaw's IEInternals, he wrote Brain Dump: International Text last month, he explained the IDN settings in this picture:
,
He also covered all of these "International' settings from the dialog.
In particular:
Send IDN server names is enabled by default and will force IE to encode hostnames in URLs following the rules of RFC3491 and RFC3492. The user will be shown the URL in the address bar in Unicode form if and only if the URL is deemed non-spoofable. Please see this IEBlog post on the rules of IDN Non-spoofability.
Send IDN server names for Intranet addresses is disabled by default for compatibility with legacy Windows networks that were using UTF-8 to support non-ASCII hostnames. Other browsers, to the best of my knowledge, do not have special handling for Intranet sites, and I believe that current versions of Active Directory and the Windows DNS server support punycoded hostname registration and lookup.
Since he did all this work, it saves me the trouble!
Kinda great teamwork, he and I.
I guess there 's no "I" in IE, either! :-)
Daniel Cheng on 10 Aug 2012 9:25 PM:
Quote from your blog:
He also covered all of these "International' settings from the dialog.
I guess you choose to use a mixing of single quote ' and double quote " here to annoy programmers like me?
Matthew Slyman on 16 Apr 2013 9:33 AM:
Excellent. Now I must get by back-side in gear and finish designing my system for multi-lingual semantic websites where the URLs themselves are localised (I mean "localized")! (Masochism perhaps, when one encounters "false friend" words that make a legal URL potentially non-unique and ambiguous between the URIs they're meant to point at... But when one sorts between the possibilities using the HTTP language preferences of the user, everything becomes clear again... I think...)
referenced by
2013/10/17 There's no "I" in IDN, part 19: There's no "I" in IPv6, either!
2013/10/08 There's no "I" in IDN, part 18: There isn't even an "I" in John C. Klensin's name!
2013/09/13 There's no "I" in IDN, part 17: EAI made it to China, and everybody knows it!
2013/04/19 There's no "I" in IDN, part 16: It's a good thing they decided to call it EAI!
2012/10/12 There's no "I" in IDN, part 15: Still no 'I' in EAI.... but we could use an US sometime soon!