No, I'm saying the reverse. The way the 05 logic is set up, the table contains the lines I quoted:<br><br>2064..2069 ; DISALLOWED # <reserved>..<reserved><br><br>I think it should not; that is, that those *should* be:<br>
<br>2064..2069 ; UNASSIGNED # <reserved>..<reserved><br><br>Part of this is, as I said, that the formulation of the rules in 05 makes it very hard to see what is happening. So it wasn't until I did a test against what I thought the logic should be that these popped out.<br>
<br>Mark<br><br><div class="gmail_quote">On Thu, Mar 20, 2008 at 7:43 AM, Paul Hoffman <<a href="mailto:phoffman@imc.org">phoffman@imc.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
At 2:10 AM -0700 3/20/08, Mark Davis wrote:<br>
>1. I just did a test of the 05 tables (against Unicode 5.0).<br>
><br>
>Other than the Cf issue, I found one other thing. There are<br>
><reserved> characters (that is, General_Category=Cn) that show up as<br>
>DISALLOWED when they shouldn't.<br>
><br>
>2064..2069 ; DISALLOWED # <reserved>..<reserved><br>
>...<br>
><br>
>I believe the reason is that they are default_ignoreable. But<br>
>General_Category=Cn should take precedence.<br>
<br>
I am not understanding the logic here. Are you saying IDNA200x should<br>
have a hole for later additions of punctuation to the Unicode<br>
Standard? We don't know the properties of those future characters.<br>
_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Mark