W3C home > Mailing lists > Public > public-powderwg@w3.org > April 2008

Re: ァ2.1.3 IRI/URI Canonicalization does not address IRIs with IDNs

From: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 10 Apr 2008 20:46:39 +0900
Message-ID: <47FDFE1F.2070001@w3.org>
To: Martin Duerst <duerst@it.aoyama.ac.jp>
CC: Phil Archer <parcher@icra.org>, Eric Prud'hommeaux <eric@w3.org>, public-powderwg@w3.org, public-i18n-core@w3.org

Martin Duerst wrote:
> At 15:00 08/04/10, Felix Sasaki wrote:
>> Hi Phil,
>> I was looking into this section in your attachment:
>> [
>> Internationalized Domain Names
>>    * Internationalized Domain Names (IDNs) should be converted from Punycode [RFC3492] into their UTF-8 string representations. So that, for example:
>>      http://www.xn--exmple-jua.org/
>>      becomes
>>      http://www.ex蚓ple.org/.
>> ]
>> If you have
>> http://www.xn--exmpless-jua.org/
>> It is not possible to decide whether it should become
>> http://www.ex蚓pless.org/
>> or
>> http://www.ex蚓ple゜.org/
>> since "ss" in the Punycode string could have been originally "ss" or "゜".
> Not exactly. IDNA defines a toASCII operation and a toUNICODE operation.
> The toUNICODE operation is well-defined, and produces "ss" in the above
> case.

many thanks for the clarification, Martin. What I wanted to say is that
in the above case you don't know what xn--exmpless-jua was generated
from, a string with ss or Eszett.


> What may be more of a complication is that the new proposals for the
> revision of the IDNA spec (IDNAbis) are proposing to move the mapping
> step out of the protocol definition. This at least leads to less
> certainity; I'm not sure how exactly it would affect POWDER.
Received on Thursday, 10 April 2008 11:47:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:06:03 UTC