more fixes for Tables

Patrik Fältström patrik at frobbit.se
Mon Feb 18 19:43:07 CET 2008


On 18 feb 2008, at 18.18, Erik van der Poel wrote:

> On Feb 16, 2008 1:31 PM, Patrik Fältström <patrik at frobbit.se> wrote:
>> List of all codepoints generated with the fixed script, one on each
>> line, can be found at http://stupid.domain.name/idnabis/f.txt
>>
>> One example of a line is the following:
>>
>> 0040   DISALLOWED  Y#        COMMERCIAL AT
>>
>> The "Y" before the # can also be an "N". This is an experiment I do
>> when checking with IDNA2003. If the Ruby library implementation of
>> libidn give as a result that nameprep(cp) == cp, then it is "Y",
>> otherwise (including if the result is "not valid"), then it is "N". I
>> do not know yet whether this check actually produce the correct  
>> result
>> regarding whether the codepoint was valid in a U-label in IDNA2003 or
>> not. I have to do more tests. Anyone else that have any ideas on what
>> one could do?
>
> I'm not sure what your goal is, but if the goal is simply to list
> whether or not a codepoint is allowed in IDNA2003, then one way to
> check the Ruby/libidn output is to test it against ICU's
> implementation of IDNA2003, for example. I'd be happy to write that
> program, if you wish.

Not if it is allowed in IDNA2003, but if it is allowed in the DNS in  
IDNA2003. I.e. what is "allowed" in IDNA2003 is also what is later  
mapped to something else. So I would like to know what codepoints  
actually could end up in DNS according to IDNA2003.

    Patrik

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.alvestrand.no/pipermail/idna-update/attachments/20080218/599cd15b/PGP.bin


More information about the Idna-update mailing list