Page Not Found

Error: Invalid Request

Comments

Re: The Inextricable Issue of Internationalized Domain Names Paul Hoffman  –  Jul 05, 2007 4:23 PM PST

What is wrong with giving India 24 TLDs? Given that the vast majority of countries have only one to three languages, is there really a problem with adding a thousand or so new TLDs? Have the people running the root servers suggested that this is an issue? If not, why assume that it is a problem?

Also, the statement that all 1652 Indic languages have their own alphabet is absurd, and certainly not supported by the reference.

Reply  |  Link  |  Report Problems
Re: The Inextricable Issue of Internationalized Domain Names Patrick Vande Walle  –  Jul 06, 2007 12:37 AM PST

There is nothing intrinsically "wrong" with allocating 24 TLDs or more for India.  From my own experience living in countries where several languages are used, there is a strong link between language, culture and political and social recognition.
ICANN may find itself in the middle of political tensions if it limits the number of accepted IDN equivalents for each ccTLD ou gTLD. The current .EH case exemplifies quite well how local political issues can have an effect on the root zone file.

As for the alphabets, Wikipedia mentions there are already 29 Brahmic scripts included in Unicode and around twenty of them not yet included. Some language like Khasmiri are written in two different scripts. I agree the "all" word should have been "many" . The main point is that it is a quite complicated matter. It will be difficult for ICANN to come up with an implementation policy that will suit everyone.

Reply  |  Link  |  Report Problems
Re: The Inextricable Issue of Internationalized Domain Names Stephane Bortzmeyer  –  Jul 06, 2007 1:59 AM PST

Also, the statement that all 1652 Indic languages have their own alphabet is absurd

Indeed, there are only 124 scripts registered (for the entire world) in ISO 15924 (http://www.unicode.org/iso15924/codelists.html) so pretending the number of scripts is a problem is pure FUD, there are less scripts than countries!

Reply  |  Link  |  Report Problems
Re: The Inextricable Issue of Internationalized Domain Names Paul Hoffman  –  Jul 06, 2007 8:23 AM PST

Patrick Vande Walle said:

ICANN may find itself in the middle of political tensions if it limits the number of accepted IDN equivalents for each ccTLD ou gTLD. The current .EH case exemplifies quite well how local political issues can have an effect on the root zone file.

It is already in the middle of them. Allowing too much or too little won't change that.

I am still interested in your response to the other questions about why you think that adding all the language equivalents is a problem. To me, unless the root server operators say it is a problem, folks like you and me should not be saying that it is. They are the ones who understand the deployment issues.

As for the alphabets, Wikipedia mentions there are already 29 Brahmic scripts included in Unicode and around twenty of them not yet included. Some language like Khasmiri are written in two different scripts. I agree the "all" word should have been "many" . The main point is that it is a quite complicated matter. It will be difficult for ICANN to come up with an implementation policy that will suit everyone.

I would disagree with "many" as well. I also don't believe that 20 of actively-used Indic scripts are not encoded. They may not be stand-alone scripts, but it is likely that all the characters they need are already encoded in the Unicode standard. I agree with Stephane: this is just FUD.

Reply  |  Link  |  Report Problems
Re: The Inextricable Issue of Internationalized Domain Names David Wrixon  –  Jul 07, 2007 2:48 AM PST

At present any substantive commitment from ICANN to do anything at all rather than simply promising to talk about more talks would be a massive step forward.

It would also help if Paul Twomey would stop pretending that ICANN is actually putting Unicode in the Root. It is not and never will. It would also be useful if he would make it abundantly clear that what ICANN is doing only affects the top level and that the biggest log jam is in fact being cause by Microsoft. It is really browser support that is critical to progress not DNS support.

Microsoft has effectively used it monopolistic position to cripple the Internets of Asia through its neglect. Disfunctional Internets are causing economic disadvantage, which is vastly outweighing any philanthropic effects it owner might be making.

Anyway payback time is coming. Supremacy in the browser wars will largely determine Microsoft's fate. If they fail to roll out IE7 to ward the dual threats from Safari and Firefox, they are doomed. Google and Apple will overrun them just as the Goths and Vandals sacked Rome. The browser is the key to the Control of the Advertising and software markets and failure to get a replacement to IE6 to market is likely to prove Microsoft's epitaph.

Reply  |  Link  |  Report Problems

To post comments, please login or create an account.