<html 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=Windows-1252">
<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{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>
</head>
<body lang="EN-US" link="#0563C1" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">That’s a lot of changes. I’ve reviewed some of them in detail and skimmed the rest.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OT 1.8.4 looks great. Thanks to all who contributed, and especially to Peter, who brought it all together in his usual masterful and balanced way – and with much good humor.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sairus<o:p></o:p></p>
<p class="MsoNormal"><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">mpeg-otspec <mpeg-otspec-bounces@lists.aau.at><br>
<b>Date: </b>Tuesday, November 10, 2020 at 3:26 PM<br>
<b>To: </b>Peter Constable <pgcon6@msn.com>, MPEG OT Spec list (mpeg-otspec@lists.aau.at) <mpeg-otspec@lists.aau.at><br>
<b>Subject: </b>Re: [MPEG-OTSPEC] OT 1.8.4 public beta review<o:p></o:p></span></p>
</div>
<p class="MsoNormal">Just a reminder: the three-week review period for the OT 1.8.4 public beta ends this Friday.<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>Peter Constable<br>
<b>Sent:</b> Saturday, October 24, 2020 2:51 PM<br>
<b>To:</b> MPEG OT Spec list (mpeg-otspec@lists.aau.at) <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> [MPEG-OTSPEC] OT 1.8.4 public beta review<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Some weeks back, I mentioned that work was being done to prepare a dot-dot update to the OpenType spec. The OpenType 1.8.4 update is now publicly available for a “beta” review:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Ftypography%2Fopentype%2Fotspec184beta%2Fot184beta&data=04%7C01%7Csppatel%40adobe.com%7Cac57b4e3a77d46b2421508d885d017a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637406476083570117%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=7li7fTASzRHurBYgPtbm7rx1WmMZjfHvde3KsQz7rU4%3D&reserved=0">https://docs.microsoft.com/en-us/typography/opentype/otspec184beta/ot184beta</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">When work started in August, there was a backlog of 99 issues that had been reported in the prior two years. After the new work began, another 141 issues were filed—a 141% increase in the past two months. Altogether, there were 240 different
pieces of feedback on the OT spec that were taken into consideration, and changes made in response to over 200 of these issues (85%). There are 27 remaining issues still open that can be considered in a subsequent version—a cut-off for this release was needed
at some point. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><i>How is this relevant for the AHG? </i><o:p></o:p></p>
<p class="MsoNormal"><i> </i><o:p></o:p></p>
<p class="MsoNormal">Most or all of the feedback given on the OT spec is also relevant for OFF. So, after considering feedback from the review period and making last changes, the result will be submitted as proposed revisions for a future edition* of OFF. Of
course, any of it would be in scope for discussion within the AHG.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">*Because there are so many edits in so many parts of the spec, it wouldn’t lend itself for the amendment process that was recently started. It might be feasible, however, to incorporate a limited selection of changes into an amendment.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The content is available at the link above for a public review period of three weeks—until November 13. Note that the beta content will get taken down after OT 1.8.4 is considered complete and becomes the current version. The beta content
includes two variants of each changed page/section: a “delta” version showing all edits with “change tracking” formatting; and a “final” version showing the results of the edits (all the deletions and “change tracking” formatting are removed). Feedback can
be submitted on any of the beta content “final” version pages using a feedback link at the bottom of the page. A best effort will be made to respond to feedback on the proposed changes. Any entirely new issues reported will likely be left for a future update.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I understand that this process isn’t everything that everyone here would like to see (e.g., people wanting the content to be treated like an OSS project), but hopefully this is seen to be a step in a good direction.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I’d like to acknowledge and thank Google Fonts and Microsoft who have made this possible.<o:p></o:p></p>
<p class="MsoNormal"> <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 Constable<o:p></o:p></p>
</div>
</body>
</html>