<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=iso-8859-1">
<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:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle21
{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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Vlad:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sorry for this late comment. After returning from holidays, Cosimo provided a comment on a particular detail in the proposed text for 5.7.11.4. While looking at that I also
noticed an issue in the same section where I had changed the example Var* structure but didn’t make a corresponding change that was needed in the following paragraph, leaving it in an incoherent state. Thus, I’ve just made a few changes in the WD content provided
in the Google Fonts repo. There are changes in three paragraphs; you can see the specific details
<a href="https://github.com/googlefonts/colr-gradients-spec/commit/9cfbcaefc88f487b547431b62dfab22ee743d9b8#diff-f8c59e8d70f0a695574ea35269cf5f70c46db8cc40daa2d5e128e8c79be10528">
here</a>. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If it’s not too late, you might want to incorporate that into the m55831 contribution.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></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;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Vladimir Levantovsky <vladimir.levantovsky@gmail.com>
<br>
<b>Sent:</b> Monday, January 4, 2021 1:33 PM<br>
<b>To:</b> 'Peter Constable' <pgcon6@msn.com>; 'MPEG OT Spec list' <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> RE: [MPEG-OTSPEC] WD for AMD 2 and COLR v1 enhancements<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Happy New Year! I hope you had a nice holiday break.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Please see attached for your review two input contributions I prepared based on the input to this AHG (and public GitHub discussions) on behalf of their respective authors.
Since I did not receive any additional comments, I intend to submit these contributions to WG document registry by end of day today.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Please also note that the contribution m55831 [summarizing COLR v1 updates] includes a number of highlighted unresolved topics that will need to be discussed as part of the
break-out group session during the week of the WG meeting (Jan. 11-15, 2021). We need to finalize them by Jan. 15 if we plan to recommend the promotion of the current Working Draft amendment to the next Committee Draft stage.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thank you all for your contributions,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">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"> Vladimir Levantovsky [<a href="mailto:vladimir.levantovsky@gmail.com">mailto:vladimir.levantovsky@gmail.com</a>]
<br>
<b>Sent:</b> Sunday, December 27, 2020 1:59 PM<br>
<b>To:</b> Peter Constable <<a href="mailto:pgcon6@msn.com">pgcon6@msn.com</a>><br>
<b>Cc:</b> MPEG OT Spec list (<a href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>) <<a href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>><br>
<b>Subject:</b> Re: [MPEG-OTSPEC] WD for AMD 2 and COLR v1 enhancements<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Hello all,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Many thanks to Peter, Rod, Dominik, and many other people who have contributed their review comments to the development and improvements of the proposed text for COLR v1 amendment.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Since the deadlines for registration and upload of input contributions is coming up soon, I would like to propose the following plan of actions:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- use the updated COLR v1 text from the public GitHub repo <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgooglefonts%2Fcolr-gradients-spec%23annex-a-proposed-changes-to-isoiec-14496-22&data=04%7C01%7C%7C4d6b63e403d54df4ac6808d8b0f857b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637453928524215397%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=cW%2FFA1%2F9HaPYiyttxYCUWpTUtwLlYyiAfrC7aVrdy00%3D&reserved=0">https://github.com/googlefonts/colr-gradients-spec#annex-a-proposed-changes-to-isoiec-14496-22</a>
as the basis for the updated proposal;<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- extend the current draft amendment with three additional amended parts proposed as part of <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMPEGGroup%2FOpenFontFormat%2Fissues&data=04%7C01%7C%7C4d6b63e403d54df4ac6808d8b0f857b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637453928524225384%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8fqTCpuPHMCVCR%2Bu4AZd1JhojWrppOMob1i%2BwfoX6Bs%3D&reserved=0">MPEGGroup/OpenFontFormat
</a>discussions (issues 36-38);<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- submit the AHG Recommendation to consider the proposed changes be used as a replacement to the current content of the Working Draft ISO/IEC 14496-22/AMD2.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Please submit your additional comments and proposed changes (if any) no later than the end of day on December 30. In absence of additional comments, and if no objections will have been raised by Dec. 30 - I will consider the current text
of the proposal, along with the additional changes, to be approved by AHG consensus.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you again for your contributions!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Vladimir<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Dec 22, 2020 at 10:00 PM Peter Constable <<a href="mailto:pgcon6@msn.com">pgcon6@msn.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">In the past few weeks, I’ve been working with Rod Sheeter and Dominik Röttsches at Google to draft updates for the working draft related to COLR version 1. This fills out details
for the new formats added in COLR version 1 as well as integrating with the existing text for COLR version 0 (which doesn’t go away).<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The proposed content for OFF Amendment 2 is available here:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgooglefonts%2Fcolr-gradients-spec%23annex-a-proposed-changes-to-isoiec-14496-22&data=04%7C01%7C%7C4d6b63e403d54df4ac6808d8b0f857b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637453928524235382%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=HkDX4Cj7k0cLO2DZ7vHRFB8RJGDUC4WRLn4CdwwtxFA%3D&reserved=0" target="_blank">https://github.com/googlefonts/colr-gradients-spec#annex-a-proposed-changes-to-isoiec-14496-22</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">When the COLR v1 enhancements were proposed here back in September, the proposal doc had specific details on the structure formats, but not much explanation of the semantics — how
the formats represent different graphic concepts and are to be processed. Much of the additional content in this draft is conceptual explanation of the graphic operations that are supported and how the structures are used to represent those, with several figures
to illustrate. The intent was not obvious before, but should be clear now with these additions.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">There have also been some further design enhancements in the proposed draft: additional paint table formats for translate, rotate and skew transformations—the separate formats are
more compact than the matrix format if only the specific transform is needed, and the rotate/skew formats specify rotation angles in degrees, which is much better when varying a rotation angle in a variable font than varying the matrix elements.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">There are a few open issues (“TBD: …” in that doc), but these are limited in scope and shouldn’t hinder revision of the working draft considered by SC29 at the January meeting.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">AHG members are invited to review and comment. I’d suggest that general comments not requiring specific action could be sent to this list, but for suggested improvement, it would
be better to track these in GitHub issues—either in the GitHub repo above or in the MPEG/OFF repo:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMPEGGroup%2FOpenFontFormat%2Fissues&data=04%7C01%7C%7C4d6b63e403d54df4ac6808d8b0f857b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637453928524235382%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9rH0N4i3mpBkDKRk%2BmqCxfP0lhjuH2aBJcUT7I%2FL0SE%3D&reserved=0" target="_blank">Issues
ˇ MPEGGroup/OpenFontFormat (github.com)</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Re COLR v1 and OpenType: I’ve been preparing a parallel draft for the next OT version. That’s in MSFT’s typography repo, which is still a private repo. The content will differ from
the OFF content only in minor, non-technical wording details.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Peter Constable<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
mpeg-otspec mailing list<br>
<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a><br>
<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.aau.at%2Fmailman%2Flistinfo%2Fmpeg-otspec&data=04%7C01%7C%7C4d6b63e403d54df4ac6808d8b0f857b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637453928524245377%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XU6yIFQKIUtoVw8l%2FrG5NHdQbk2Gft1MzR5B6eC79rc%3D&reserved=0" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>