<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Good call, that is much clearer.<br>
</p>
<div class="moz-cite-prefix">On 2021-01-09 09:34, Peter Constable
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DM5PR1301MB210899FD7A30DAD390A96A9686AD0@DM5PR1301MB2108.namprd13.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@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;}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;}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}span.EmailStyle23
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0in;}ul
{margin-bottom:0in;}</style>
<div class="WordSection1">
<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"
moz-do-not-send="true">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 class="moz-txt-link-rfc2396E" 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 class="moz-txt-link-rfc2396E" 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>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph"
style="color:#1F497D;margin-left:0in;mso-list:l0 level1
lfo2">
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></li>
<li class="MsoListParagraph"
style="color:#1F497D;margin-left:0in;mso-list:l0 level1
lfo2">
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></li>
<li class="MsoListParagraph"
style="color:#1F497D;margin-left:0in;mso-list:l0 level1
lfo2">
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></li>
<li class="MsoListParagraph"
style="color:#1F497D;margin-left:0in;mso-list:l0 level1
lfo2">
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></li>
<li class="MsoListParagraph"
style="color:#1F497D;margin-left:0in;mso-list:l0 level1
lfo2">
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"
moz-do-not-send="true">
proposed changes</a> in the last two paragraphs.<o:p></o:p></li>
</ul>
<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"
moz-do-not-send="true">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"
moz-do-not-send="true">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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
mpeg-otspec mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>
<a class="moz-txt-link-freetext" href="https://lists.aau.at/mailman/listinfo/mpeg-otspec">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Chris Lilley
@svgeesus
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture & Technology Team, Core Web & Media</pre>
</body>
</html>