No subject


Wed Jan 29 08:39:27 CET 2020 

The Unicode Consortium publishes a document "UAX 31 - Identifier and Patter=
n Syntax" to assist in the standard treatment of identifiers in UCS charact=
er-based parsers. Those specifications are recommended for determining the =
list of UCS characters suitable for use in identifiers. The document is ava=
ilable at http://www.unicode.org/reports/tr31/.





If you want a descriptive name that is not the actual name of the file, the=
n I would refer to it as "the Unicode Character Database file for joining-s=
cript properties."





Peter



-----Original Message-----
From: John Hudson [mailto:john at tiro.ca]
Sent: Tuesday, September 13, 2016 6:47 PM
To: Levantovsky, Vladimir <Vladimir.Levantovsky at monotype.com>
Cc: Peter Constable <petercon at microsoft.com>; mpeg-OTspec at yahoogroups.com
Subject: Re: [mpeg-OTspec] DAM2 comments



On 13/09/16 09:37, Levantovsky, Vladimir wrote:



> I am not sure what should be considered the name of the document though s=
ince it's a simple text file and the name of the file (ArabicShaping.txt) i=
sn't something I'd consider human friendly.



That is the name, though. Within each version of the file is a longer name =
containing the version, e.g.



     # ArabicShaping-9.0.0.txt



Like many of the normative data files of the Unicode Standard, it is intend=
ed to be machine parseable as well as humanly readable, hence the file name=
 is the normative reference.



J.





--



John Hudson

Tiro Typeworks Ltd    www.tiro.com<http://www.tiro.com>

Salish Sea, BC        tiro at tiro.com<mailto:tiro at tiro.com>



Getting Spiekermann to not like Helvetica is like training a cat to stay ou=
t of water. But I'm impressed that people know who to ask when they want to=
 ask someone to not like Helvetica. That's progress. -- David Berlow



--_000_SN1PR0301MB1966817E925C92D3C5FCFA40D5FE0SN1PR0301MB1966_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">If precedents would help, here are several exampl=
es of this kind of thing from ISO/IEC 10646:2014 (which doesn’t have =
any “Bibliography” section):<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText"><i>From clause 6.4:<o:p></o:p></i></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">The list of character names, except for CJK unifi=
ed ideographs and Hangul syllables, is provided in 31.<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in">NOTE – The list =
of character names is also part of the Unicode character Database in:
<a href=3D"http://www.unicode.org/Public/UNIDATA/NamesList.txt">http://www.=
unicode.org/Public/UNIDATA/NamesList.txt</a> with the syntax described in:
<a href=3D"http://www.unicode.org/Public/UNIDATA/NamesList.html">http://www=
.unicode.org/Public/UNIDATA/NamesList.html</a>.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText"><i>From Clause 16.6.2:</i><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in">NOTE 1 – The con=
tent is also available as a separate viewable file in the same file directo=
ry as this document. The file is named “UCSVariants.txt”. These=
 sequences are also described as
<i>StandardizedVariants.html</i> in the Unicode character data-base (http:/=
/www.unicode.org/Public/UNIDATA/StandardizedVariants.html).<o:p></o:p></p>
<p class=3D"MsoPlainText"><a name=3D"_MailEndCompose"><o:p> </o:p></a>=
</p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><i>F=
rom clause 16.6.3:</i><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"mso-boo=
kmark:_MailEndCompose">NOTE – This International Standard incorporate=
s by reference the variation sequences listed in version 2010-11-14 of the =
Ideographic Variation Database, as described
 at </span><a href=3D"http://www.unicode.org/ivd/data/2012-03-02/"><span st=
yle=3D"mso-bookmark:_MailEndCompose">http://www.unicode.org/ivd/data/2012-0=
3-02/</span><span style=3D"mso-bookmark:_MailEndCompose"></span></a><span s=
tyle=3D"mso-bookmark:_MailEndCompose">.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><o:p=
> </o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><i>F=
rom clause 25:</i><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"mso-boo=
kmark:_MailEndCompose">NOTE 3 – All the allowed Named UCS Sequence Id=
entifiers for use with this International Standard are also listed in the U=
nicode character database:
</span><a href=3D"http://www.unicode.org/Public/UNIDATA/NamedSequences.txt"=
><span style=3D"mso-bookmark:_MailEndCompose">http://www.unicode.org/Public=
/UNIDATA/NamedSequences.txt</span><span style=3D"mso-bookmark:_MailEndCompo=
se"></span></a><span style=3D"mso-bookmark:_MailEndCompose">.<o:p></o:p></s=
pan></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><o:p=
> </o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><i>F=
rom Annex U:</i><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"mso-boo=
kmark:_MailEndCompose">The Unicode Consortium publishes a document "UA=
X 31 – Identifier and Pattern Syntax" to assist in the standard =
treatment of identifiers in UCS character-based parsers.
 Those specifications are recommended for determining the list of UCS chara=
cters suitable for use in identifiers. The document is available at
</span><a href=3D"http://www.unicode.org/reports/tr31/"><span style=3D"mso-=
bookmark:_MailEndCompose">http://www.unicode.org/reports/tr31/</span><span =
style=3D"mso-bookmark:_MailEndCompose"></span></a><span style=3D"mso-bookma=
rk:_MailEndCompose">.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><o:p=
> </o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><o:p=
> </o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose">If y=
ou want a descriptive name that is not the actual name of the file, then I =
would refer to it as “the Unicode Character Database file for joining=
-script properties.”<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><o:p=
> </o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><o:p=
> </o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose">Pete=
r<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"mso-bookmark:_MailEndCompose"><o:p=
> </o:p></span></p>
<span style=3D"mso-bookmark:_MailEndCompose"></span>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: John Hudson [mailto:john at tiro.ca] <br>
Sent: Tuesday, September 13, 2016 6:47 PM<br>
To: Levantovsky, Vladimir <Vladimir.Levantovsky at monotype.com><br>
Cc: Peter Constable <petercon at microsoft.com>; mpeg-OTspec at yahoogroups=
.com<br>
Subject: Re: [mpeg-OTspec] DAM2 comments</p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">On 13/09/16 09:37, Levantovsky, Vladimir wrote:<o=
:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">> I am not sure what should be considered the =
name of the document though since it's a simple text file and the name of t=
he file (ArabicShaping.txt) isn't something I'd consider human friendly.<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">That is the name, though. Within each version of =
the file is a longer name containing the version, e.g.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">     # ArabicShaping-9.0.0.tx=
t<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">Like many of the normative data files of the Unic=
ode Standard, it is intended to be machine parseable as well as humanly rea=
dable, hence the file name is the normative reference.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">J.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">-- <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">John Hudson<o:p></o:p></p>
<p class=3D"MsoPlainText">Tiro Typeworks Ltd    <a href=3D"h=
ttp://www.tiro.com"><span style=3D"color:windowtext;text-decoration:none">w=
ww.tiro.com</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText">Salish Sea, BC     &nbsp=
;  <a href=3D"mailto:tiro at tiro.com"><span style=3D"color:windowtext;te=
xt-decoration:none">tiro at tiro.com</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
<p class=3D"MsoPlainText">Getting Spiekermann to not like Helvetica is like=
 training a cat to stay out of water. But I'm impressed that people know wh=
o to ask when they want to ask someone to not like Helvetica. That's progre=
ss. -- David Berlow<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p> </o:p></p>
</div>
</body>
</html>

--_000_SN1PR0301MB1966817E925C92D3C5FCFA40D5FE0SN1PR0301MB1966_--

More information about the mpeg-otspec mailing list