<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Peter, <div><br></div><div>You can separate the issues that are require substantive changes from those that are purely editorial, and then group them together in multiple input contributions (by topic, by subclause, etc) like it was done for CFF2, where contents of one subclause and two annexes were restructured and combined in a single contribution. </div><div><br></div><div>I cannot make structural changes in the text of the standard on a whim, we need to follow an established ISO process. <br><br><div dir="ltr"><div>Thank you,</div>Vlad</div><div dir="ltr"><br><blockquote type="cite">On Apr 6, 2022, at 11:40 AM, Peter Constable <pconstable@microsoft.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<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:"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:"Noto Sans";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
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>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Vlad:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">You didn’t respond to my question, which is of more concern to me: how would you suggest I compile an input contribution that covers almost 300 issues?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Vladimir Levantovsky <vladimir.levantovsky@gmail.com><br>
<b>Date: </b>Tuesday, April 5, 2022 at 9:47 PM<br>
<b>To: </b>Peter Constable <pconstable@microsoft.com><br>
<b>Cc: </b>MPEG OT Spec list <mpeg-otspec@lists.aau.at><br>
<b>Subject: </b>Re: [EXTERNAL] RE: [MPEG-OTSPEC] FYI: OpenType 1.9 beta<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Peter,<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">There are certain changes that indeed can be considered purely editorial - typos, clarification and restructuring individual sentences for clarity would be suitable examples of such changes. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">However, when you would like to make more substantive changes, such as structural changes that rearrange content of sub clauses, they need to be presented and reviewed by the WG. A good, very recent example
of such change would be the content of CFF2 table description (sub clause 5.4.3). The revised text didn’t introduce technical changes but due to substantial rewrite and restructuring of the text, it was proposed as input contribution and then adopted as part
of this new 5th edition Working Draft.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt">We need to follow the same path for all structural changes, even though if a change isn’t technical and doesn’t affect conformance. <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Thank you,<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Vlad<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt">On Apr 5, 2022, at 1:11 PM, Peter Constable <pconstable@microsoft.com> wrote:<o:p></o:p></span></p>
</blockquote>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Vlad:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I think I’d consider the structural changes to be editorial in nature. (E.g., conformance was not affected by those changes.) Of course, they were not minor edits.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">All of the changes to the OT spec not reflected in Amd 2 were addressing a number of issues reported against the spec:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">1.8.4: </span><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Ftypography-issues%2Fissues%3Fq%3Dis%253Aissue%2Bmilestone%253A%2522OpenType%2B1.8.4%2522&data=04%7C01%7Cpconstable%40microsoft.com%7C16b2800301d84e83279208da17889909%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637848172700817568%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=qb%2F8nFxjc0eTOMd8s%2FkRfzAREHLRddhPNRhuJ%2BSeJII%3D&reserved=0">Issues
· MicrosoftDocs/typography-issues (github.com)</a> (count: 236)<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Post 1.8.4 errata: </span><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Ftypography-issues%2Fissues%3Fq%3Dis%253Aissue%2Bmilestone%253A%2522OpenType%2B1.8.4%2Berratum%2522&data=04%7C01%7Cpconstable%40microsoft.com%7C16b2800301d84e83279208da17889909%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637848172700817568%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=2i8poFVBYZFVlP7mBmw4zX0RAvVJ1DrQgLGidWoZBOU%3D&reserved=0">Issues
· MicrosoftDocs/typography-issues (github.com)</a> (count: 2)<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">1.9: </span><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Ftypography-issues%2Fissues%3Fq%3Dis%253Aissue%2Bmilestone%253A%2522OpenType%2B1.9%2522&data=04%7C01%7Cpconstable%40microsoft.com%7C16b2800301d84e83279208da17889909%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637848172700817568%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=DtBToCcPAT4rBXGWUspnGUfY8JcgU%2FxrEPIkGcj5Ub0%3D&reserved=0">Issues
· MicrosoftDocs/typography-issues (github.com)</a> (count: 56)<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">How would you suggest I compile an input contribution for all of that?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Vladimir Levantovsky <vladimir.levantovsky@gmail.com><br>
<b>Date: </b>Monday, March 28, 2022 at 2:00 PM<br>
<b>To: </b>Peter Constable <pconstable@microsoft.com>, 'MPEG OT Spec list' <mpeg-otspec@lists.aau.at><br>
<b>Subject: </b>[EXTERNAL] RE: [MPEG-OTSPEC] FYI: OpenType 1.9 beta</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Peter, all,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I would like to note that a large number of substantial changes were made in the two last updates of OpenType specification, versions 1.8.4 and 1.9. While major updates (COLR v1) have been discussed
and implemented in both OT and OFF texts, there are many additional changes that introduced text updates that go beyond merely editorial changes. Some parts of the OT spec were subjected to restructuring that, although they did not introduce technical changes,
caused significant deviation in the language of the current OT chapters and OFF text.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">In order to implement these changes and synchronize the text of the 5<sup>th</sup> edition Working Draft OFF text with OT 1.8.4 and 1.9 updates, the updates will need to be submitted as input
contributions.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thank you,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Vladimir</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><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><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> mpeg-otspec [mailto:mpeg-otspec-bounces@lists.aau.at]
<b>On Behalf Of </b>Peter Constable<br>
<b>Sent:</b> Friday, November 12, 2021 1:31 AM<br>
<b>To:</b> 'MPEG OT Spec list' <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> [MPEG-OTSPEC] FYI: OpenType 1.9 beta</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p style="margin:0in;background:white;vertical-align:baseline"><span style="font-size:12.5pt;font-family:"Noto Sans",sans-serif;color:black">A beta for OpenType 1.9 has been published for two-week public review. This version aligns to the CDAM of OFF Amendment
2 with the introduction of a significant enhancement for colour fonts: a <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftypedrawers.com%2Fhome%2Fleaving%3FallowTrusted%3D1%26target%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Ftypography%252Fopentype%252Fotspec190%252Fcolr&data=04%7C01%7Cpconstable%40microsoft.com%7C16b2800301d84e83279208da17889909%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637848172700817568%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fK5b%2BwIO%2FM9a6g9IWFJzBtQGP%2Fqa8gvL9FaRr8wDiWA%3D&reserved=0"><span style="color:#1E79A7;border:none windowtext 1.0pt;padding:0in">second
version of the COLR table</span></a> (version 1). </span><o:p></o:p></p>
<p style="margin:0in;background:white;vertical-align:baseline"><span style="font-size:12.5pt;font-family:"Noto Sans",sans-serif;color:black"> </span><o:p></o:p></p>
<p style="margin:0in;background:white;vertical-align:baseline"><span style="font-size:12.5pt;font-family:"Noto Sans",sans-serif;color:black">The new COLR version provide support for gradients and other capabilities in vector colour fonts; the capabilities are
very similar to those in SVG Native but can be used in applications that do not have or (for whatever reasons) cannot add support SVG. The new COLR version also provides greater integration with font variations—something that is not supported at all with OT-SVG.
The COLR enhancements were designed jointly with Google, who have been implementing support in the FontTools project, the Skia and Freetype libraries, and in Chrome. It can be tested already in the <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftypedrawers.com%2Fhome%2Fleaving%3FallowTrusted%3D1%26target%3Dhttps%253A%252F%252Fwww.google.com%252Fchrome%252Fcanary%252F&data=04%7C01%7Cpconstable%40microsoft.com%7C16b2800301d84e83279208da17889909%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637848172700817568%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BZAlVWozUHq0gvCNsszUlI0gXSrU7gDXbWjLBMApmBI%3D&reserved=0"><span style="color:#1E79A7;border:none windowtext 1.0pt;padding:0in">Chrome
Canary</span></a> builds by browsing to chrome://flags/#colr-v1-fonts to enable the feature. Sample fonts using COLR v1 (with OT-SVG equivalents for comparison) are available at <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftypedrawers.com%2Fhome%2Fleaving%3FallowTrusted%3D1%26target%3Dhttps%253A%252F%252Fgithub.com%252Fgooglefonts%252Fcolor-fonts&data=04%7C01%7Cpconstable%40microsoft.com%7C16b2800301d84e83279208da17889909%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637848172700817568%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=mk%2FfL2T3fq70%2FpBuDMaI9nH6Y85C2rt1KzDvnQvuMh4%3D&reserved=0" title="Link: https://github.com/googlefonts/color-fonts"><span style="color:#1E79A7;border:none windowtext 1.0pt;padding:0in">https://github.com/googlefonts/color-fonts</span></a>. </span><o:p></o:p></p>
<p style="mso-margin-top-alt:7.5pt;margin-right:0in;margin-bottom:10.5pt;margin-left:0in;background:white;vertical-align:baseline">
<span style="font-size:12.5pt;font-family:"Noto Sans",sans-serif;color:black">OpenType 1.9 also addresses a number of feedback items that have been reported on the OpenType spec. Among the more significant technical improvements are clarifications of several
items related to TrueType outlines and the TrueType hinting language. These are changes that will be submitted to SC29 as proposed changes for a new edition of OFF.</span><o:p></o:p></p>
<p style="margin:0in;background:white;vertical-align:baseline;text-rendering: optimizelegibility !important;outline: 0px;word-break:break-word;text-overflow: ellipsis;font-variant-ligatures: normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-webkit-text-stroke-width: 0px;text-decoration-thickness: initial;text-decoration-style: initial;text-decoration-color: initial;word-spacing:0px">
<span style="font-size:12.5pt;font-family:"Noto Sans",sans-serif;color:black">The landing page for the beta is at <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftypedrawers.com%2Fhome%2Fleaving%3FallowTrusted%3D1%26target%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Ftypography%252Fopentype%252Fotspec190%252Fot190beta&data=04%7C01%7Cpconstable%40microsoft.com%7C16b2800301d84e83279208da17889909%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637848172700817568%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=DUxNdJOtZSGwBiJpuiCDXDDXrBncD4aaity3MTjrtUo%3D&reserved=0" title="Link: https://docs.microsoft.com/typography/opentype/otspec190/ot190beta"><span style="color:#1E79A7;border:none windowtext 1.0pt;padding:0in">https://docs.microsoft.com/typography/opentype/otspec190/ot190beta</span></a>.
The public review period will end November 26, and the new OT version will be published shortly after that.</span><o:p></o:p></p>
<p style="margin:0in;background:white;vertical-align:baseline"><span style="font-size:12.5pt;font-family:"Noto Sans",sans-serif;color:black"> </span><o:p></o:p></p>
<p style="margin:0in;background:white;vertical-align:baseline"><span style="font-size:12.5pt;font-family:"Noto Sans",sans-serif;color:black"> </span><o:p></o:p></p>
<p style="margin:0in;background:white;vertical-align:baseline"><span style="font-size:12.5pt;font-family:"Noto Sans",sans-serif;color:black">Peter Constable</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</div></blockquote></div></body></html>