IDNNever.txt

Vint Cerf vint at google.com
Sun Mar 4 23:56:06 CET 2007


The IANA IDN tables are pretty old by now and should be updated once the new
character sets have been assigned new nomenclature: never, always, pending.


Vinton G Cerf
Chief Internet Evangelist
Google
Regus Suite 384
13800 Coppermine Road
Herndon, VA 20171
 
+1 703 234-1823
+1 703-234-5822 (f)
 
vint at google.com
www.google.com
 

-----Original Message-----
From: idna-update-bounces at alvestrand.no
[mailto:idna-update-bounces at alvestrand.no] On Behalf Of fujiwara at jprs.co.jp
Sent: Sunday, March 04, 2007 4:04 AM
To: kenw at sybase.com
Cc: idna-update at alvestrand.no
Subject: Re: IDNNever.txt

> From: Kenneth Whistler <kenw at sybase.com> 
> http://www.unicode.org/~whistler/IDNNever.txt
> That has the same format as:
> http://www.unicode.org/~whistler/IDNPermitted.txt

Hi,

I compared these two tables with IANA registered IDN tables.

IANA IDN Registry is 
     http://www.iana.org/assignments/idn/registered.htm

I found two characters which are listed in IDNNever table and listed in
'th-thai' table.

th-thai.html:U+002e: defined but IDNNever
th-thai.html:U+0e33: defined but IDNNever

# U+002E defined in th-thai table should be a mistake, I think.
# I don't know about U+0E33 character.

I found six characters which are not listed in IDNPermitted table but listed
in IANA Registered IDN tables.

jp-japanese.html     U+3007
jp-japanese.html     U+30fb
pl-greek.html	     U+0390
pl-greek.html	     U+03b0
th-thai.html	     U+002e
th-thai.html	     U+0e33

jp-japanese table case, U+3007 and U+30FB are used in proper nouns in JAPAN.

--
Kazunori Fujiwara, JPRS
_______________________________________________
Idna-update mailing list
Idna-update at alvestrand.no
http://www.alvestrand.no/mailman/listinfo/idna-update



More information about the Idna-update mailing list