<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">i agree with mark on the titling matter.<div><br></div><div>as to the code points, we should surely include all that are part of the unicode scope.</div><div><br></div><div>vint</div><div><br></div><div><br><div><div>On Nov 22, 2009, at 1:09 PM, Mark Davis ☕ wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><a href="http://unicode.org/Public/UNIDATA/UnicodeData.txt" target="_blank">http://unicode.org/Public/UNIDATA/UnicodeData.txt</a> is only part of the Unicode data; if you only look at that file, you get a very incomplete view of the Unicode data and properties. It doesn't list reserved characters, so for example, <br> <pre>F0000;<Plane 15 Private Use, First>;Co;0;L;;;;;N;;;;;<br>FFFFD;<Plane 15 Private Use, Last>;Co;0;L;;;;;N;;;;;<br>100000;<Plane 16 Private Use, First>;Co;0;L;;;;;N;;;;;<br>10FFFD;<Plane 16 Private Use, Last>;Co;0;L;;;;;N;;;;;<br>
</pre>You don't see the code points U+FFFFE and U+FFFFF either. The fact that Unicode goes from 0..10FFFF is in the core specification (see <a href="http://www.unicode.org/versions/Unicode5.2.0/">http://www.unicode.org/versions/Unicode5.2.0/</a>). UTS #44 Unicode Character Database (<a href="http://www.unicode.org/reports/tr44/">http://www.unicode.org/reports/tr44/</a>) should also be referenced, since it explains the data formats.<br> <br>As for the titles, I think the more important feature is having either all or none of them start with "Internationalized Domain Names for Applications (IDNA):", and having Tables and Bidi in in the titles.<br> <br clear="all">Mark<br> <br><br><div class="gmail_quote">On Fri, Nov 20, 2009 at 13:16, Harald Alvestrand <span dir="ltr"><<a href="mailto:harald@alvestrand.no" target="_blank">harald@alvestrand.no</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div>Mark Davis ☕ wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I noticed in <a href="http://tools.ietf.org/id/draft-ietf-idnabis-tables-07.txt" target="_blank">http://tools.ietf.org/id/draft-ietf-idnabis-tables-07.txt</a> the following:<br> <br> E01F0..EFFFD; UNASSIGNED # <reserved>..<reserved><br> <br> EFFFE..10FFFE; DISALLOWED # <noncharacter>..<noncharacter><br> It is missing 10FFFF.<br> </blockquote> <br></div> The Unicode data table /UnicodeData.txt) doesn't tell us what 10FFFE and 10FFFF are; the last character listed is 10FFFD (Plane 16 Private Use, Last).<br> <br> On the other hand, Blocks.txt says:<br> <br> unicode/Blocks.txt:100000..10FFFF; Supplementary Private Use Area-B<br> <br> So is there a distinction between 10FFFD, 10FFFE and 10FFFF, and does this document need to make that distinction?<br> <br> (I think it's unreasonable to allow any of them in domain names, so they should all be DISALLOWED, but i'm not surprised that there's inconsistencies here.)<div><br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> The titles of the documents are inconsistent: The first three below have a prefix, and the last 3 are missing it. Also, the first three use titlecase (Background, Explanation, and Rationale have B, E, and R capitalized), and the next two don't. It might also be nice to have "BIDI" someplace in "Right-to-left scripts for IDNA", and "Tables" somewhere in "The Unicode code points and IDNA"<br> </blockquote></div> The RFC Editor has strong opinions on where to use titlecase. I always get changes when I submit RFCs, so I have left that evaluation on his table.<br> <br> <br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> * Internationalized Domain Names for Applications (IDNA):<div><br> Definitions and Document Framework -<br> <a href="http://tools.ietf.org/html/draft-ietf-idnabis-defs" target="_blank">http://tools.ietf.org/html/draft-ietf-idnabis-defs</a><br> * Internationalized Domain Names in Applications (IDNA): Protocol<br> - <a href="http://tools.ietf.org/html/draft-ietf-idnabis-protocol" target="_blank">http://tools.ietf.org/html/draft-ietf-idnabis-protocol</a><br> * Internationalized Domain Names for Applications (IDNA):<br> Background, Explanation, and Rationale -<br> <a href="http://tools.ietf.org/html/draft-ietf-idnabis-rationale" target="_blank">http://tools.ietf.org/html/draft-ietf-idnabis-rationale</a><br> * Right-to-left scripts for IDNA -<br> <a href="http://tools.ietf.org/html/draft-ietf-idnabis-bidi" target="_blank">http://tools.ietf.org/html/draft-ietf-idnabis-bidi</a><br> * The Unicode code points and IDNA -<br> <a href="http://tools.ietf.org/html/draft-ietf-idnabis-tables" target="_blank">http://tools.ietf.org/html/draft-ietf-idnabis-tables</a><br> * Mapping Characters in IDNA -<br> <a href="http://tools.ietf.org/html/draft-ietf-idnabis-mappings" target="_blank">http://tools.ietf.org/html/draft-ietf-idnabis-mappings</a><br> <br> <br> <br> Mark<br></div><div> ------------------------------------------------------------------------<br> <br> _______________________________________________<br> Idna-update mailing list<br> <a href="mailto:Idna-update@alvestrand.no" target="_blank">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> <br> </div></blockquote> <br> <br> </blockquote></div><br> _______________________________________________<br>Idna-update mailing list<br><a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>http://www.alvestrand.no/mailman/listinfo/idna-update<br></blockquote></div><br></div></body></html>