<div dir="ltr">Thank you Thomas for sharing this.<div>We still have time to postpone the call by another week, if it is beneficial for all involved. My main goal is [ideally] to address the issues we already identified before the holiday season is upon us, and still have time in early January for one final review (if necessary), before the next input submission deadline on January 15, 2024, with the WG meeting happening on January 22-26.</div><div><br></div><div>Folks, would the alternative dates of either Dec. 12 or Dec. 14 work better for all involved?</div><div><br></div><div>Thank you,</div><div>Vladimir</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 17, 2023 at 12:10 PM Thomas Phinney <<a href="mailto:thomas.phinney@gmail.com">thomas.phinney@gmail.com</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"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">That is the same time as the ATypI AGM (announcement going out today), and also during the Brazilian diaTipo conference.</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">T</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 17, 2023 at 8:46 AM Vladimir Levantovsky <<a href="mailto:vladimir.levantovsky@gmail.com" target="_blank">vladimir.levantovsky@gmail.com</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"><div dir="ltr">Dear all,<div><br></div><div>Based on the limited number of responses, I decided to schedule the AHG Zoom call the week of Dec. 4-8. The primary consideration for this choice is to allow authors more time to work on the updated proposal and produce an updated document addressing the issues and comments that were discussed at the WG meeting in October.</div><div><br></div><div>I propose that we should consider scheduling the meeting on either Dec. 5 or Dec. 7 at 15:00 UTC to accommodate different time zones (7:00 am US Pacific / midnight in Tokyo, with everyone else in between). If you have a conflict with any or both of the proposed dates - please suggest another day. </div><div><br></div><div>If I do NOT hear from you, I will assume that the proposed dates are fine, and will schedule the call on Dec. 7 at 15:00 UTC.</div><div><br></div><div>Thank you,</div><div>Vladimir</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 15, 2023 at 5:14 PM Behdad Esfahbod <<a href="mailto:behdad@behdad.org" target="_blank">behdad@behdad.org</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"><div dir="ltr"><div dir="ltr">On Wed, Nov 15, 2023 at 8:05 AM Dominik Röttsches <<a href="mailto:drott@google.com" target="_blank">drott@google.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> please respond to this email to indicate your availability and specific date preferences for the call. </blockquote><div><br></div><div>FWIW, I prefer the week of Nov 27. - the week after I likely have a work trip and there's a public holiday and - for many - a long weekend in Finland.</div></div></blockquote><div><br></div><div>Nov 27 works for me. I'll be traveling the rest of that week. I'm available the week after it though.</div><div><br></div><div>b</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Dominik</div><div><br></div><div><br></div><div> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 15, 2023 at 12:57 AM Vladimir Levantovsky <<a href="mailto:vladimir.levantovsky@gmail.com" target="_blank">vladimir.levantovsky@gmail.com</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"><div dir="ltr">Dear all,<br><div><br></div><div>Following up on my previous email, I am happy to let you know that the text of the updated <a href="https://www.mpeg.org/wp-content/uploads/mpeg_meetings/144_Hannover/w23170.zip" style="box-sizing:border-box;opacity:0.9;font-family:Arial,Helvetica,sans-serif,Arial,Helvetica,sans-serif;font-size:14.4px" target="_blank">WD of ISO/IEC 14496-22 5th edition Open Font Format</a> is now available for public review. </div><div><br></div><div>While integrating the proposed changes related to newly introduced Condition Table Format 2 (see subclause 6.2.9) I realized that the current description of the Condition Table is technically incorrect since it is referring to non-existent version number of the ConditionSet table (see second paragraph). It appears that <a href="https://learn.microsoft.com/en-us/typography/opentype/spec/chapter2#featurevariations-table" target="_blank">the corresponding parts of the OpenType spec</a> have already been modified at some point but these text modifications/corrections have not been proposed to the SC29/WG3 yet.</div><div><br></div><div>I also would like to remind you that we need to schedule the AHG Zoom call to further discuss the changes necessary to make progress on the "Beyond 64K glyphs" proposal summarized in the "<a href="https://www.mpeg.org/wp-content/uploads/mpeg_meetings/144_Hannover/w23265.zip" style="box-sizing:border-box;opacity:0.9;font-family:Arial,Helvetica,sans-serif,Arial,Helvetica,sans-serif;font-size:14.4px" target="_blank">Technologies under consideration for ISO/IEC 14496-22 5th edition Open Font Format</a>" document. Our available options are to schedule the first call either during the week of Nov. 27 or the week of Dec. 4 - please respond to this email to indicate your availability and specific date preferences for the call. </div><div>(I am hopeful that the additional changes we discussed during the last WG meeting would already be integrated in the updated version of the proposal that we can review and finalize during the call.)<br></div><div><br></div><div>Thank you,</div><div>Vladimir</div><div><br></div><div><br></div><div> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 10, 2023 at 4:31 PM Vladimir Levantovsky <<a href="mailto:vladimir.levantovsky@gmail.com" target="_blank">vladimir.levantovsky@gmail.com</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"><div dir="ltr">Dear all,<br><div><br></div><div>Following the last WG03 meeting, we've got an updated set of mandates - published as WG03N01013 approved at the ISO SC29/WG3 meeting that took place on Oct. 16-20, 2023. </div><div>Our new mandates for the period until the next WG meeting (scheduled on January 22-26, 2024) are as follows:</div><div><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">1. Review the text of the updated Working Draft of ISO/IEC 14496-22 5th edition (WG03N01017).<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">2. </span>
<span style="font-size:10pt;font-family:"Courier New"">Review the content of the “Technologies under
consideration” document (WG03N01081), work on developing and finalizing
specification changes to accommodate larger character sets and new features,
prepare an updated input contribution and provide recommendations for the WG3
on how these changes should be integrated in the “Open Font Format” standard</span><span style="font-size:10pt;font-family:"Courier New"">.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10pt;font-family:"Courier New"">3. Explore potential future changes and updates, and propose new items (if applicable) for consideration in the 5th edition of the OFF specification.</span><u></u><u></u></p><p class="MsoNormal"><u></u> </p><p class="MsoNormal">The updated text of the ISO/IEC 14496-22 Working Draft (WG03N01017) will be made available for public review soon, and I will provide a link to it as soon as it is uploaded. Meanwhile, the "<a href="https://www.mpeg.org/wp-content/uploads/mpeg_meetings/144_Hannover/w23265.zip" style="box-sizing:border-box;opacity:0.9;font-family:Arial,Helvetica,sans-serif,Arial,Helvetica,sans-serif;font-size:14.4px" target="_blank">Technologies under consideration for ISO/IEC 14496-22 5th edition Open Font Format</a>" document [based on the input contribution we discussed at the WG meeting] has already been published, and, according to our mandate #2, we should continue reviewing it to prepare the updated input contribution and provide AHG recommendations for the WG3.</p><p class="MsoNormal"><br></p><p class="MsoNormal">ISO rules require that the AHG meeting announcements should be made at least two weeks in advance. Our earliest opportunity to schedule the AHG meeting will be the week of Nov. 27 (immediately following the Thanksgiving holidays in the US), or we can postpone it until next week, Dec. 4-8, 2023. Please let me know what dates work best for you.</p><p class="MsoNormal"><br></p><p class="MsoNormal">Following our previously established practice, the AHG meeting date and agenda will be shared on this list, but the meeting Zoon link will not be, due to this list having a public archive. Everybody who has been a participant in the prior AHG meetings will be automatically invited to the future AHG meeting as well - if you have not participated in the AHG meetings in the past and would like to be added to the guest list - please to this email directly and I will gladly accommodate any and all requests.</p><p class="MsoNormal"><br></p><p class="MsoNormal">Stay tuned for an additional announcement of updated Working Draft availability - I will share a document link on this list as soon as it's published.</p><p class="MsoNormal"><br></p><p class="MsoNormal">Thank you,</p><p class="MsoNormal">Vladimir</p><p class="MsoNormal"> </p></div></div>
</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>
_______________________________________________<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></div>
</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>
</blockquote></div>