<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: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:"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:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I am afraid that the post below manifests a lack of understanding of the role the AHG plays.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The AHG has never meant to usurp the power to be the only venue for font technology development – its role is to establish the forum where new ideas and new technical
proposals can be discussed and contributed for OFF standardization, regardless of whether a contribution comes from an individual or a corporate entity, whether the proposal is aiming to provide clarifications and minor updates to existing part of the standard,
or if it comes as a result of collaborative development by multiple parties with the goal to introduce significant new functionality and tools.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Your examples of collaborative developments that happened independently and at different times under the auspices of the Unicode Consortium, and the fact that
these proposals have been submitted via AHG and integrated in numerous amendments and new editions of the OFF standard only confirm the fact that the AHG fulfills its obligations to the type community. Whether a new proposal undergoes further discussions and
updates or whether it is adopted as presented based on the AHG consensus doesn’t change the fact that this AHG enabled unrestricted access to standardization activities for all interested parties, regardless of their affiliation and participation status.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">It is also important to mention that while anyone can submit a proposal, any member of the AHG can raise an objection to a submitted proposal based on its technical
merits - even if a proposal has major implementer standing behind it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Vladimir<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> mpeg-otspec <mpeg-otspec-bounces@lists.aau.at>
<b>On Behalf Of </b>Behdad Esfahbod<br>
<b>Sent:</b> Saturday, September 26, 2020 3:27 AM<br>
<b>To:</b> mpeg-otspec <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> [MPEG-OTSPEC] To add some more perspective<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">and respond to some of the recent commentary on the list:<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Since 2014 the <a href="mailto:opentype-layout@unicode.org" target="_blank">
opentype-layout@unicode.org</a> mailing list has been the <i>de facto</i> embodiment of the MPEG Open Font Format Ad-Hoc Group.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Since 2016 the <a href="mailto:otfontvar@unicode.org" target="_blank">
otfontvar@unicode.org</a> mailing list has been the embodiment of the MPEG Open Font Format Ad-Hoc Group in matters of Variable Fonts.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">So whenever "drafts" came down <i>here</i>, on this list, for "review", they <b>never</b> had any
<i>real</i> chance to be <b>meaningfully</b> altered through feedback on this list. What is offered by the chair on this list for review is to double-check his copy/paste and search/replace work as well as spot typos and grammatical mistakes and suggest improved
wording. Otherwise the <i>actual</i> work has already happened in meetings, most of them I / Google(+Facebook) hosted (opentype-layout + half of otfontvar), the rest Peter / Microsoft hosted.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I put together the agenda and chaired the opentype-layout ones. Peter managed the otfontvar ones. In all cases only Peter had the pen, and access to make changes appear in OpenType, and by the time they arrived at this list for "review"
they were well underway to ship in Windows, making the <i>technical essence</i> unchangeable unless to address major deficiencies (eg. STAT).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">behdad<br>
<a href="https://protect-us.mimecast.com/s/fbceC0Rmp0u2kByruwvVfJ/" target="_blank">http://behdad.org/</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>