Browser IDN display policy: opinions sought

Abdulrahman I. ALGhadir aghadir at
Wed Dec 21 09:42:51 CET 2011

I think currently both ICANN and IANA maintain a public list for new IDNs and their supported script/language, see the 2 lists:
 - IANA :

These 2 lists can be easily combined and amended with some extra fields to suit the application developer needs. For example, additional field can be added to cover supported languages and scripts that will help applications safely to display U-Labels instead of A-Labels when the language/script rules is met.


-----Original Message-----
From: idna-update-bounces at [mailto:idna-update-bounces at] On Behalf Of Gervase Markham
Sent: 19/Dec/2011 1:42 PM
To: Raed Al-Fayez
Cc: idna-update at
Subject: Re: Browser IDN display policy: opinions sought

Hi Raed,

Thank you for your input.

I would say that the vendor you quote is using sloppy language and it's not actually about 'prioritizing English', but your point about first-class citizenship is a good one.

If all registries were are responsible as yours, there would hardly be a need for browser restrictions on IDN display at all (perhaps just a blacklist of homographs for "." and "/", and that should have been achieved by IDNA2008 anyway).

> IDNs should not be treated as second-class citizens on the Internet.

I entirely agree. This is why we went for option B - once a registry has a responsible policy, their IDNs are treated as first-class citizens everywhere (at least, in Firefox). No additional configuration required.

Unfortunately, IDNs are still not treated as first-class citizens. So the question is: how do we get from where we are now to a situation where they are treated that way?

Idna-update mailing list
Idna-update at

This message and its attachment, if any, are confidential and may contain legally
privileged information. If you are not the intended recipient, please contact the
sender immediately and delete this message and its attachment, if any, from your
system. You should not copy this message or disclose its contents to any other
person or use it for any purpose. Statements and opinions expressed in this e-mail
are those of the sender, and do not necessarily reflect those of the Communications
and Information Technology Commission (CITC). CITC accepts no liability for damage
caused by this email.

More information about the Idna-update mailing list