<span class="q"><br></span><div style="direction: ltr;">> I take it this means the answer to my question is "no", since the script<br>> names in Scripts.txt and the ISO 15924 codes don't match up.<br><br>
<br></div>We need to drag you, kicking and screaming, into ever deeper understanding of how Unicode works.<br><br>Each Unicode property name, and property value name may have aliases. These aliases, as you would expect, are encapsulated in a machine-readable file, such as
<a href="http://www.unicode.org/Public/UNIDATA/PropertyValueAliases.txt">http://www.unicode.org/Public/UNIDATA/PropertyValueAliases.txt</a><br><br>So, for example, you see there:<br><span><br><span style="font-family: courier new,monospace;">
sc ; Arab ; Arabic</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">sc ; Armn ; Armenian</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">
sc ; Bali ; Balinese</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">sc ; Beng ; Bengali</span><br>...<br><br>The first field, sc, is the short name for the "script" property; Armn is the short name for one of its values (which corresponds to the 15924 code), and Armenian is the long name used in the data file
Script.txt. If you look at the site for the 15924 Registration Authority (<a href="http://www.unicode.org/iso15924/">http://www.unicode.org/iso15924/</a>), you'll find also in the tables such as <a href="http://www.unicode.org/iso15924/iso15924-codes.html">
http://www.unicode.org/iso15924/iso15924-codes.html</a> a listing of both the long and short value names.<br><br></span><span>The Unicode script property (</span>2001-02-06) actually predated first publication of ISO 15924 (2004-01-09), however, it was done in the knowledge that 15924 was coming, and they have been kept in sync since.
<br><span><br>Mark<br><br></span><div><span class="gmail_quote">On 12/19/06, <b class="gmail_sendername">Harald Alvestrand</b> <<a href="mailto:harald@alvestrand.no">harald@alvestrand.no</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;">
Thanks for pointing out the relevant TR for the use of script codes, and<br>the special status of "Common" and "Inherited". The algorithm grows....<br><br>--On 19. desember 2006 12:45 -0800 Kenneth Whistler <
<a href="mailto:kenw@sybase.com">kenw@sybase.com</a>> wrote:<br><br>>> Is there a list of the Unicode codepoints known to be used in each of<br>>> the ISO 15924 script codes?<br>><br>> That is an ill-formed question. ISO 15924 defines script codes.
<br>> It does not define repertoires or associate code points with<br>> those script codes. So you can't have sets of Unicode code points<br>> "in each ISO 15924 script code".<br>><br>> The closest you are going to get to an repertoire partitioning
<br>> of Unicode into scripts is Scripts.txt, the very file we have<br>> been talking about and using for the development of the<br>> inclusions file.<br><br>I take it this means the answer to my question is "no", since the script
<br>names in Scripts.txt and the ISO 15924 codes don't match up.<br><br> Harald<br><br><br><br><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">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br></blockquote></div><br>