Chinese IDNs have arrived

ICANN gave approval to Chinese IDNs — for China, Taiwan, and Hong Kong.

This is a significant development — particularly since China was one of the major forces pushing ICANN to support IDNs.

To give you an idea of how these new IDNs are poised to change the Internet as we know it, I’ve overlayed the approved IDNs onto my Country Codes of the World map.

You’ll notice both simplified and traditional script IDNs for both China and Taiwan.

Here’s my running list of all IDNs that have passed string evaluation stage.

The dawn of a new URL

ICANN announced today that its first full-length IDN has gone live.

Here it is: http://وزارة-الأتصالات.مصر

Give it a test drive.

I just did (on the Mac) and Firefox, Safari, and Chrome all worked fine. Here is Safari:

Safari is unique in that it left the URL as is instead of converting it into its “punycode” equivalent shown below:

Firefox, Chrome, and Safari all manage and display IDNs a little bit differently. I have my two cents on how they “should” handle IDNs and I’ll be writing about that shortly.

In the meantime, I’m just thrilled to see a real live full-length IDN.

This is the beginning of the end of the last two roadblocks to a truly multilingual Internet.

A few updates:

Here’s the BBC take.

And as “F Wolff” noted in his comment, this URL above is not the first full-length IDN ever; ICANN has been testing full-length IDNs for some time here. But my point here is that IDNs are now publicly available — in Egypt at least — with many more to come.

And, to clarify, partial IDNs have also been around for years. It was the supporting of IDNs at the top level that has finally enabled the creation of fully non-Latin domains.

So here is Egypt’s IDN:

If you look at the first browser screen grab above, you’ll notice that this string is on the far  left, not on the right, as it is a bidirectional script. But when a bidirectional script gets displayed as punycode, in the second sreen grab, the entire text string is flipped back to left-to-right order.

I find it interesting that the first batch of IDNs to go live also happen to be among the most challenging to support — not just in browser windows but across so many other software applications. But for those working in software globalization, these are exciting challenges!

ICANN approves IDNs for China, Taiwan, Thailand, Sri Lanka…

A few weeks back I asked Where is China’s IDN?

ICANN not only answered my question about China, but also about a host of additional countries (and territory) that had applied for fast-track IDNs.

Here are the most recent IDN (string evaluation) approvals:

  • China (cn): 中國 (traditional); 中国 (simplified)
  • Hong Kong (hk): 香港
  • Palestinian Territory (ps): فلسطين
  • Qatar (qa): قطر
  • Sri Lanka (lk): ලංකා (Sinhalese); இலங்கை (Tamil)
  • Taiwan (tw):  台湾 (simplified); 台灣 (traditional)
  • Thailand (th): ไทย
  • Tunisia (tn):  تونس

For the full list of IDNs now in the ICANN pipeline, I’ve created a page here. It also explains why you may not be able to view all of the scripts on this blog post.

ICANN says it has given preliminary approval for IDNs in 19 countries across 11 languages. Note that this means that these IDNs have passed the string review, which is arguably the most difficult phase. But there is still one stage left before those domains can go live. And don’t get me started on the challenges that some of these domains will pose to existing web browsers — that’s the topic of a future post.