Punycode & IMA/EAI
tina.dam at icann.org
Wed May 21 21:57:03 CEST 2008
I don't think I understand why this email-list/group is spending time discussing how popular or not popular IDNs are going to be....the matter of the fact is that IDNs exists at the second level under numerous TLDs, and there are processes underway aiming at making it available at the top level as well.
So, there really is no need to talk about "whether or not" or "how successful or useful" - the development on both technical and policy side are underway and as far as I believe that decision was made some time ago and is not up for debate today.
If you want to talk about usability or try things out, one good place to do that is on the IDN wiki: http://idn.icann.org
> -----Original Message-----
> From: idna-update-bounces at alvestrand.no [mailto:idna-update-
> bounces at alvestrand.no] On Behalf Of Martin Duerst
> Sent: Wednesday, May 21, 2008 2:46 AM
> To: John C Klensin; Felix Sasaki; Shawn Steele
> Cc: idna-update at alvestrand.no
> Subject: Re: Punycode & IMA/EAI
> At 15:01 08/05/21, John C Klensin wrote:
> >--On Wednesday, 21 May, 2008 11:15 +0900 Felix Sasaki
> ><fsasaki at w3.org> wrote:
> >> Often business cards in Japan (and I assume in other countries
> >> as well) have two sides, one with information in English, one
> >> with information in the native language. The mail address
> >> written on both sides is the same, but sometimes the URI
> >> (company homepage) is different: English homepage versus
> >> "native" homepage. So far I have never seen an URI written
> >> with non-ASCII characters written on a business card, no
> >> matter which side.
> >Nor have I.
> I have. A Japanese friend of mine had a Japanese IDN on the
> Japanese side of his business card. A single observance, still,
> but existing in reality.
> >And, if that trend continues and generalizes, then this entire
> >IDN exercise (new versions and old) and probably the EAI one are
> >a waste of time. For some reason, a lot of people don't believe
> The main blockers currently remain, which are the not yet close
> to complete coverage of IDN-capable browsers (getting better with
> the replacement of IE6 by IE7) and the lack of IDN TLDs
> (ICANN is working on it, so it can only be a matter of time :-(.
> Regards, Martin.
> #-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
> #-#-# http://www.sw.it.aoyama.ac.jp
> mailto:duerst at it.aoyama.ac.jp
> Idna-update mailing list
> Idna-update at alvestrand.no
More information about the Idna-update