2008/8/30 Per Jessen <[EMAIL PROTECTED]>:
> tedd wrote:
>
>> What some browser developers did was to NOT make the conversion from
>> PUNYCODE to the correct code-points but rather show the PUNYCODE
>> "as-is", which was never the intent of the IDNS WG. This act defeated
>> the entire process of allowing non-English people to have non-English
>> domain names. This like throwing the baby out with the bath water.
>
> But that's not what FF does though - it has no problem with other domain
> names with international characters.  For instance, the normal Danish,
> German, French, Spanish and Icelandic characters work just fine. I have
> a testing domain which contains an 'ë' - also no problem. It seems to
> be just somewhat limited to those (and others I'm sure).

True...

Firefox holds a whitelist of toplevel domains that are allowed to
display unicode (to see the list go to about:config and enter
IDN.whitelist into the filter box).

It does not allow .com domains to contain unicode for obvious phishing
reasons, but if I temporarily add it to the whitelist, I can see tedds
yin-yang domain in all its glory. Although not, for some reason which
I can't be bothered investigating, the rx-2 domain.

-robin

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to