<br><br><div><span class="gmail_quote">On 2/1/07, <b class="gmail_sendername">Kenneth Whistler</b> <<a href="mailto:kenw@sybase.com">kenw@sybase.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>> --On 14. desember 2006 18:24 -0800 Kenneth Whistler <<a href="mailto:kenw@sybase.com">kenw@sybase.com</a>> wrote:<br>><br>> > The *table* itself should unambiguously be defined as<br>> > the list of characters appropriate for inclusion in
<br>> > IDNA. IDNAInclusion.txt (or whatever name you like).<br>></blockquote><div><br>From the above, I get the feeling that you are proposing a static list of characters. If, however, you are suggesting that the list of characters is one that is included in UCD with every new version/errata of Unicode, and is derived from a set of properties, then I think it makes sense.
<br><br>Is IDNPermitted.txt the new name for it?<br><br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The statement of the IDNA nameprep, however it gets worked out
<br>in detail, is going to need an inclusion table. </blockquote><div><br>But we aren't actually going to list the characters in the new spec. It'll just be a reference to something like:<br><a href="http://www.unicode.org/Public/UNIDATA/IDNPermitted.txt">
http://www.unicode.org/Public/UNIDATA/IDNPermitted.txt</a><br><br>Right?<br></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>I just pushed up
IDNPermitted.txt to demonstrate what the<br>documentation for such a binary character property could (and<br>probably would) look like, if published as part of the Unicode<br>Character Database. The property is then easy to refer to
<br>and easy to implement.</blockquote><div><br>+1.<br> <br></div><br></div>=wil