Browser IDN display policy: opinions sought

Abdulrahman I. ALGhadir aghadir at
Sat Dec 24 06:47:37 CET 2011

I guess you have missed something.
The second link was broken I didn't copy it correctly and I think that you haven't check it, have you?

When you want to register an IDN you should define the script and the language which your label will follow. (check 3.2) (check 1.3.1)

As you see it is part from ICANN application process and it is a must and I think this will help us in having a solid resource which can provide us with needed information?

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

On 21/12/11 08:42, Abdulrahman I. ALGhadir wrote:
> I think currently both ICANN and IANA maintain a public list for new 
> IDNs and their supported script/language, see the 2 lists: - IANA :
> - ICANN:
> tion-en.htm
>  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.

Hi Abdulrahman,

As I understand it, these sites are merely records of policy; no restrictions are imposed. So if .newtld decided to register with IANA to say "we accept every character", then the tables would duly record that fact, despite there being a big potential problem.

So, unless I have missed something, such lists are of no help in this situation.


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