Re: Why ICANN TLD Policy Imposes Severe Constraint on Development of Internationalize
with the look up table of of all IDN's being (XN--"whatever")
XN-- is 4 characters long in ASCII last time I looked at the ISO table . (grin)
Isn't every CJK character going to be significantly longer than 4 ASCII characters as an IDN TLD in the root zone in any event ?
This visual restriction is a European literature/social bias.
Granted Arabic, Urdu, Farsi, Russian, Hebrew, Hindi, and Thai could have 1 and 2 character IDN GTLD's ....
I have not seen any comments anywhere, demanding this etc....so if anyone has some URL's here....please post.
But the demand and obviousness for those languages is zero in this technical regard.
Regardless of the fact that the Japanese and Korean markets are very advanced and comfortable with dot JP and dot KR, the Chinese market would
warrant special consideration here.
It is a 5000 year old language.
It has tens of thousands of characters.
Granted, simplified is not simplified to a Westerner learning the language. (grin)
CJK experts have had a solution for a decade, and have been politically sensitive with each other.... ( very historically significant I might add...with
Japanese colonization of Korea....and Chinese sensitivity to odd kanji meanings )
Granted....I am financially tied to dot com's and dot CN's in 70% of my portfolio.
Inhibiting CJK for very narrowminded policy wonk reasons, because of
Northern European language expert fairness is wrong.
ICANN is going to punt this down the track for a year until GTLD window for
dot NYC and the cctld fast track is out.
This could have been resolved in Sydney.