<div dir="ltr">I'd prefer to schedule the first AHG Zoom call on Feb. 20 as well. <div>However, in order to make the AHG call productive, I want to make sure that authors have enough time to prepare the draft proposals for discussion, and that these drafts will be available for meeting participants to review at least a few days before the meeting, e.g. by Feb. 15.<div>Let's see what responses we get until the end of this week, and decide when it would be reasonable / realistic to schedule the call on Feb. 20.</div><div><br></div><div>Thanks,</div><div>Vladimir</div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 29, 2024 at 9:10 PM Skef Iterum via mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<p>Note to Peter and anyone else with input on the feature
variations draft: I'll need feedback by February 8th or so in
order to turn around a more spec-oriented draft in time for review
before a meeting around the 20th. <br>
</p>
<p><br>
</p>
<p>I can probably make a February 20th time-frame work but I'm
drafting some additional proposals. One is a small change to CFF2
stem ordering requirements, one is a section to add to VARC about
hinting when composing CFF2 sources.</p>
<p>It may (or may not) make sense to split the discussion across
multiple meetings. We can evaluate that once there are drafts. <br>
</p>
<p>Skef<br>
</p>
<div>On 1/29/24 11:23, Vladimir Levantovsky
via mpeg-otspec wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Dear all,<br>
<div><br>
</div>
<div>During last week, at the SC29/WG3 meeting, the AHG on Font
Format was re-established by the WG3 to conduct our work until
the next WG meeting that will take place on April 22-26. As
usual, the input contribution registration deadline for the
next meeting is Monday, April 15 (a week prior to the
meeting).</div>
<div><br>
</div>
<div>The updated AHG mandates approved by the SC29/WG3 are as
follows:</div>
<div><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">1.
Review the text of the
updated Working Draft of ISO/IEC 14496-22 5<sup>th</sup>
edition (WG03N01099).<br>
2. Work on developing and finalizing specification changes
to </span><span style="font-size:10pt;font-family:Arial,sans-serif">accommodate
new ‘dmap’ table and new Feature Variations proposal<span style="color:black">, prepare input contributions and
provide recommendations for the WG3 on how these changes
should be integrated
in the “Open Font Format” standard.<br>
3. Explore potential future changes and updates, and
propose new items (if
applicable) for consideration in the 5<sup>th</sup>
edition of the OFF
specification.</span></span><br>
</div>
<div><span style="font-size:10pt;font-family:Arial,sans-serif"><span style="color:black"><br>
</span></span></div>
<div><span style="font-size:10pt;font-family:Arial,sans-serif"><span style="color:black">Due to significant changes being
introduced in the Working Draft, the WG has approved an
extended editing period and the text of the WD of </span></span><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:13.3333px">ISO/IEC
14496-22 5</span><sup style="color:rgb(0,0,0);font-family:Arial,sans-serif">th</sup><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:13.3333px"> edition
(WG03N01099) will not be available for review until after
the edits are made. This, however, should not stop us from
continuing our work on the second mandate to finalize the
'dmap' table and new "Feature Variations" proposals. I would
like to ask the prospective authors to start preparing the
detailed drafts that can be discussed by the AHG members
online and during our Zoom meetings.</span></div>
<div><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:13.3333px"><br>
</span></div>
<div><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:13.3333px">As
far as meeting schedule is concerned, I'd suggest to
consider scheduling the first AHG meeting on either Feb. 20
(Tuesday) or Feb. 21 (Wednesday) at our usual time (15:00
UTC) to give authors and the AHG members enough time to work
on the proposals and still have reasonable time left for
follow up discussions. Please let me know (prospective
authors in particular) if you believe this would be a
reasonable timeline for early draft discussions, or if we
should consider postponing the first AHG meeting until the
last week of February. The AHG meetings have to be announced
at least 2 weeks ahead of the meeting date, so we have until
Feb. 6 to decide whether this proposed AHG meeting schedule
would work.</span></div>
<div><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:13.3333px"><br>
</span></div>
<div><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:13.3333px">Thank
you,</span></div>
<div><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:13.3333px">Vladimir</span></div>
<div><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:13.3333px"><br>
</span></div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
mpeg-otspec mailing list
<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>
<a href="https://lists.aau.at/mailman/listinfo/mpeg-otspec" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a>
</pre>
</blockquote>
</div>
_______________________________________________<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://lists.aau.at/mailman/listinfo/mpeg-otspec" rel="noreferrer" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br>
</blockquote></div>