<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=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:700739457;
mso-list-template-ids:-582982784;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1800687496;
mso-list-type:hybrid;
mso-list-template-ids:-560016686 -1619902102 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:16;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Thank you Peter,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Since the nature of this typographic/formatting change is purely editorial, I don’t think we need to bring this to the WG to discuss – I can easily incorporate your proposed changes when editing the text of the updated Working Draft of the amendment.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thank you,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Vladimir<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='color:#1F497D'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Peter Constable [mailto:pgcon6@msn.com] <br><b>Sent:</b> Saturday, January 9, 2021 2:34 AM<br><b>To:</b> Vladimir Levantovsky <vladimir.levantovsky@gmail.com>; 'MPEG OT Spec list' <mpeg-otspec@lists.aau.at><br><b>Subject:</b> RE: [MPEG-OTSPEC] Draft AHG report for your review<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Vlad:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Another late comment—something to consider in the WG discussion: While re-reading the draft text for 5.7.11.1.6, there are references to “source in” and “source out” compositing modes that aren’t set apart typographically, and that makes the wording a bit confusing. For example, “The same effects can be implemented… by… selecting the source in composite mode.”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the proposed WD content in the Google Fonts repo, I’ve made changes to the typography so that the compositing mode names are always italicized and follow the capitalization in the W3C doc; this makes the meaning in the text clearer. The above example becomes, “… by… selecting the <i>Source In </i>composite mode.” You can see the specific changes in this commit:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="https://github.com/googlefonts/colr-gradients-spec/commit/2938cb91372f4bfbd2460139131f09bcf9687be3#diff-f8c59e8d70f0a695574ea35269cf5f70c46db8cc40daa2d5e128e8c79be10528">https://github.com/googlefonts/colr-gradients-spec/commit/2938cb91372f4bfbd2460139131f09bcf9687be3#diff-f8c59e8d70f0a695574ea35269cf5f70c46db8cc40daa2d5e128e8c79be10528</a><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 <<a href="mailto:mpeg-otspec-bounces@lists.aau.at">mpeg-otspec-bounces@lists.aau.at</a>> <b>On Behalf Of </b>Vladimir Levantovsky<br><b>Sent:</b> Friday, January 8, 2021 2:40 PM<br><b>To:</b> 'MPEG OT Spec list' <<a href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>><br><b>Subject:</b> Re: [MPEG-OTSPEC] Draft AHG report for your review<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Folks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I have not received any responses / comments on the draft AHG report – it will be presented as is.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Also, for the next week’s breakout session on Font Format work – so far I’ve got the following topics we need to cover to finalize the text of the amendment:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>In 5.7.11.1.2.1 Color Lines: when it comes to color interpolation, currently the spec says that color values along the color line are linearly interpolated – is this enough?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>In 5.7.11.1.2.2 Linear Gradients: the description of the gradient and rotation vectors, and effects the rotation vector has on the final results are underspecified. Issues that need additional clarifications include <br>a) rotation effect on color interpolation results if the angular distance between gradient orientation vector and rotation vector are more than 90 degrees in either direction (CW or CCW), and<br>b) what effect , if any, the magnitude of the rotation vector has. (Currently, the spec is silent about it.)<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>In 5.7.11.1.2.3 Radial Gradients: what is the expected behavior in case where both circles overlap with r > 0?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>In 5.7.11.1.2.3 Radial Gradients: specify the expected behavior in case where a transform flattens both circles and their centers to a line.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 lfo3'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>In 5.7.11.4 COLR table and OFF font variations – discuss and incorporate the <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgooglefonts%2Fcolr-gradients-spec%2Fcommit%2F9cfbcaefc88f487b547431b62dfab22ee743d9b8%3Fshort_path%3Df8c59e8%23diff-f8c59e8d70f0a695574ea35269cf5f70c46db8cc40daa2d5e128e8c79be10528&data=04%7C01%7C%7C78bfaa9cdc704f11c56808d8b4265b9d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637457424142250657%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Zn4ENHOcALtXtMvURnSMQKg%2FgLBbShw4dVNhJLRJ5jo%3D&reserved=0">proposed changes</a> in the last two paragraphs.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>If anything is missing from this list, please let me know.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thank you,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Vladimir<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><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>From:</b> Vladimir Levantovsky [<a href="mailto:vladimir.levantovsky@gmail.com">mailto:vladimir.levantovsky@gmail.com</a>] <br><b>Sent:</b> Wednesday, January 6, 2021 7:47 PM<br><b>To:</b> 'MPEG OT Spec list' <<a href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>><br><b>Subject:</b> Draft AHG report for your review<br><b>Importance:</b> High<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dear all,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please see attached the draft of the AHG report that I will present at the upcoming MPEG Systems (SC29/WG3) meeting next week (Jan. 11 – 15). Your comments are appreciated.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We do have a number of open issues that need to be resolved in order to finalize COLR v1 specification – it would be best if these issues are resolved by next week, and discussed as part of the Font Format break-out group session during the WG meeting. Currently, this break-out session is tentatively scheduled on January 13 at 21:00 UTC. We will be using one of the available ISO Zoom rooms; however, the meeting access information will only be available to WG members and cannot be shared publicly.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I would like to bring your attention to the specific part of the AHG Recommendations section where a promotion of the current Working Draft to the next PDAM stage is suggested (last paragraph, also highlighted). The final outcome related to document promotion will likely be determined based on the results of the WG discussions. Our possible options are to either keep the document as the Working Draft and finalize all remaining issues before the next WG meeting in early April, or to recommend promoting the document to the next PDAM stage, and address the remaining _<i>minor</i>_ issues as part of the ballot comments. I’d like to remind you that in order to be able to process the ballot in time for the next meeting, it will likely be published as two-months ballot, and the time period for submission of comments will be very short (most National Bodies require comments to be submitted at least three weeks prior to ballot closing date).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please respond to this email with any proposed changes and corrections to the AHG report by the end of day Friday, Jan. 8<sup>th</sup> – No comments will be interpreted as approval!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you,<o:p></o:p></p><p class=MsoNormal>Vladimir<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>