RE: Unicode & ICANN Part 3

From: Jony Rosenne (
Date: Sun Aug 31 2008 - 14:23:05 CDT

  • Next message: Doug Ewell: "Re: Unicode & ICANN Part 3"

    Is there a reason why Punycode cannot be restored to Unicode when being displayed to humans?


    -----Original Message-----
    From: [] On Behalf Of Doug Ewell
    Sent: Sunday, August 31, 2008 8:12 PM
    To: Unicode Mailing List
    Subject: Re: Unicode & ICANN Part 3

    What exactly are you trying to accomplish here?

    URLs were originally designed to be ASCII-only and there is a huge
    amount of infrastructure that now relies on this. IDNA and Punycode
    were developed to make internationalized domain names work within the
    existing infrastructure. The IDNA Working Group within IETF chose not
    to consider "purer" proposals that would have broken the existing
    Internet infrastructure.

    I recommend visiting the IDNA Working Group at, reading their
    mail archives and getting familiar with the work they are already doing
    in this regard. That will probably achieve more than sending messages
    like this to top executives at ICANN and PIR.

    Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14  
    ----- Original Message ----- 
    From: "linuxa linux" <>
    To: <>
    Sent: Sunday, August 31, 2008 5:24
    Subject: Unicode & ICANN Part 3
    > List
    > I would like to thank those that have answered the Unicode & ICANN 
    > postings to this list.  There is another issue for discussion and your 
    > answers and criticism would really help:
    > Due to the ASCII character encoding being the core/monopoly and 
    > primarily basis to the internet/web infrastructure that has become the 
    > conventional starting point for subsequent Unicode and Punycode 
    > character encoded internet/web, this has brought usability and 
    > integration problems for a truly multilingual internet/web because 
    > presently you cannot have domain names that are multilingual, for 
    > example: japanese and english language mixed character domain names, 
    > hindi and english language mixed character domain names etc.
    > Another example, there is not much browser / URL bar integration and 
    > usability innovation that allow for a non-ASCII language domain name 
    > to stay non-ASCII script on the browser / URL bar without it changing 
    > to Punycode.
    > Thus there is a basic underlying problem that can only be rectified 
    > when all the languages get represented on the internet/web 
    > infrastructure and not only ASCII character encoded languages.  ASCII 
    > monopoly has not helped usability and integration for the internet/web 
    > and a Unicode approach is need.  Unicode has accomplished things at 
    > the non-internet computer ground and now it needs to expand at the 
    > internet/web ground.  Otherwise things are not equal between the ASCII 
    > and non-ASCII languages.  For example you are seeing Punycode and not 
    > the non-ASCII script for non-ASCII domain names on the browser / URL 
    > bars -- a solution for this example here could perhaps be to have even 
    > ASCII based domain names to be also Punycoded as a standard not just 
    > non-ASCII based domain names to be Punycoded, thus bringing equality. 
    > When you get equality between the two then there will be browser / URL 
    > bar integration and usability innovation simultaneously between all 
    > the
    > languages.  I put this to Tina Dam at ICANN, the person handling these 
    > issues and Paul Twomey, the ICANN President/CEO and Pamela Miller at 
    > PIR the .ORG registry a few months ago however there was not much 
    > progress with them.
    > Regards
    > Meeku

    This archive was generated by hypermail 2.1.5 : Sun Aug 31 2008 - 14:25:39 CDT