<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Angsana New";
panose-1:2 2 6 3 5 4 5 2 3 4;}
@font-face
{font-family:"Cordia New";
panose-1:2 11 3 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Well, that certainly seems like a reason why language systems and features need to remain organized by scripts.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Now, in some OT2.0 future, maybe new formats could be created in which language systems don’t use OT tags at all but use BCP-47 tags directly. Then that would address that issue. And if ‘loc’ features were organized that way but other features
don’t need to be shoe-horned into that structure, we could still have features applied script boundaries triggering lookups that can act on glyphs of whatever scripts.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> mpeg-otspec <mpeg-otspec-bounces@lists.aau.at> <b>
On Behalf Of </b>John Hudson<br>
<b>Sent:</b> Friday, August 21, 2020 3:09 PM<br>
<b>To:</b> mpeg-otspec@lists.aau.at<br>
<b>Subject:</b> Re: [MPEG-OTSPEC] <span style="font-family:"MS Gothic"">回复</span>: [EXTERNAL] Re: Shaping behavior standardization: multi-engine or "Super USE"?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 21082020 1:52 pm, Peter Constable wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Thirdly, if there is one shaping engine for all scripts, would there be any need at all for LangSys and Feature tables to still be organized hierarchically under different script tags? (That’s another existing obstacle to glyph actions
across script-run boundaries.) IOW, instead of a new _<i>set</i>_ of script tags, would just _<i>one</i>_ new “script” tag suffice?
<o:p></o:p></p>
</blockquote>
<p>That’s where my mind started going today. But I'm not sure all the issues that arise can be resolved in that model.<o:p></o:p></p>
<p>If itemisation and glyph run segmentation is not performed on the basis of script tag, and everything using the new USE tag gets processed as a single run, how do we handle characters with locl substitution forms specific to individual scripts? And if such
characters are Unicode script=common, are we pushing the segmentation down a level rather than removing it?<o:p></o:p></p>
<p>J.<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>John Hudson<o:p></o:p></pre>
<pre>Tiro Typeworks Ltd <a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.tiro.com%2F&data=02%7C01%7C%7C1616133818014946dfec08d8461ec268%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637336445210466153&sdata=3QXIbesjKK19iu5KzdBIWKhrBQT4pesrueVYEB1%2FkNc%3D&reserved=0">www.tiro.com</a><o:p></o:p></pre>
<pre>Salish Sea, BC <a href="mailto:tiro@tiro.com">tiro@tiro.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>NOTE: In the interests of productivity, I am currently <o:p></o:p></pre>
<pre>dealing with email on only two days per week, usually <o:p></o:p></pre>
<pre>Monday and Thursday unless this schedule is disrupted <o:p></o:p></pre>
<pre>by travel. If you need to contact me urgently, please <o:p></o:p></pre>
<pre>use some other method of communication. Thank you.<o:p></o:p></pre>
</div>
</body>
</html>