There has been some (appropriate) concerns on the too large character set available for idn, such as spoofing domain names. The brute force cure is to show the encoded version (xn--viagnie-eya.com) to the user instead of the decoded version (viagénie.com) of the idn. Therefore, some top-level DNS registries have applied some restrictive rules on the possible set of characters that can be registered in the domain names under their authority, some haven't. There is work currently to update the idn specification to be more restrictive in the use of inappropriate characters in idn.
By the principle of precaution, Firefox developers decided to disable the decoding of idn for the TLD registries that do not have sufficient restrictive rules (on the judgement of the developers). The drawback of this is that, by default, for some tlds, idn displays well (i.e. viagénie.biz), for some tlds, idn are displayed un-decoded (ie. xn--viagnie-eya.com). Other browser vendors have different ways: always decode, never decode, ....
One of the tld registry in the list of non-decoded idn in Firefox is .com, but .biz is decoded. Type in the url box of your browser:
- http://www.viagénie.com
To force Firefox to enable IDN and to decode .com idn, do the following:
- about:config" in the url box.
- filter "idn"
- make sure that network.enableIDN is set to True
- add a new item: "network.IDN.whitelist.com" as a boolean and set it to true. (to add a new item, go to the up-right corner and option click the little icon there: took me a while to find it out!)
Disclosure Note: I was the co-chair of the IETF working group on idn and am co-author of some parts of the whole specification(RFC 3454, RFC 3491). So yes, I'm partly responsible for this not perfect idn solution that needs improvement. But I think that even in the current shape, it is still good enough technology to make the Internet more ready for everybody in any language.
Technical references:
