<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:"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;
font-family:"Calibri",sans-serif;
color:#1F497D;}
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;}
/* List Definitions */
@list l0
{mso-list-id:989796258;
mso-list-type:hybrid;
mso-list-template-ids:-1088226030 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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">Dear AHG members,<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 hope you are doing well and you and your families have not been directly affected by the current COVID-19 pandemic.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I haven’t seen any responses to my previous email (below) and I am wondering if this may have something to do with the list changes. If you could please let me know that you do receive emails coming from the
new email list, I would very much appreciate it.<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">Like I mentioned in my previous email, we have received a lisaison statement from the W3C CSS Working Group that identified a number of potential technical issues to consider for either clarifications or updates.
I figured I’d try and take a first stub at it, to see how we can prioritize future work. Following the same order in which these issues are listed in CSS liaison (</span><a href="https://lists.w3.org/Archives/Public/www-archive/2020Feb/att-0005/CSS-SC29-20200113.pdf">https://lists.w3.org/Archives/Public/www-archive/2020Feb/att-0005/CSS-SC29-20200113.pdf</a><span style="color:#1F497D">),
I’d like to make the following notes:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Lack of font metrics for writing systems other than Western and CJK<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Additional discussions are needed, we may need to consult with outside experts who are familiar with typographic environments of different languages and writing systems to consider the additional complexities
associated with languages like Thai [where glyphs are often composed with multiple marks positioned above and below the base].<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Italic / Oblique default angle<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Additional discussion [to fully consider the application scope of this feature] is needed.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Compatibility problem with ‘vert’<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The discussion linked from </span>
<a href="https://lists.w3.org/Archives/Public/www-archive/2019Dec/">https://lists.w3.org/Archives/Public/www-archive/2019Dec/</a>
<span style="color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%">
seem to be specific to a particular behavior of existing version of Adobe InDesign application and Adobe Japanese font set. Considering the recent changes introduced by ISO/IEC 14496-22:2019/AMD1, I am not sure how much more (if anything) need to be done on
the spec side. I do realize that both applications and fonts need to be updated to be compliant with new feature descriptions.</span><span style="color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Clarifications for ‘vert’<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It appears that this particular issues has been addressed by the AMD1, additional discussion may be needed.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Clarifications for Bopomofo<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Additional discussion is needed.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Cursive elongation<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It appears that this requested functionality may already be enabled by the existing JUST table implementation; it is not obvious [without further discussion with CSS] whether additional clarifications or technical
changes are needed.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">7.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Fidelity of font metrics<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Based on the problem description, it appears that additional discussion and longer-term collaboration with CSS WG is needed to understand and hopefully help solve the issues they experience.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">8.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Required vs. Optional ligatures<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">See </span><a href="https://github.com/w3c/csswg-drafts/issues/2644">https://github.com/w3c/csswg-drafts/issues/2644</a><span style="color:#1F497D"> for problem description. Additional information and discussions
may be needed.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">9.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Overline Metrics<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">This is a request to consider adding overline capabilities to OFF (similar to how underline position is currently defined in fonts). Additional discussion is needed.<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">Your comments / suggestions / proposals are very much appreciated!<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>
<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 <mpeg-otspec-bounces@lists.aau.at> <b>
On Behalf Of </b>Levantovsky, Vladimir via mpeg-otspec<br>
<b>Sent:</b> Thursday, February 13, 2020 11:52 AM<br>
<b>To:</b> mpeg-otspec@lists.aau.at<br>
<b>Cc:</b> mpeg-OTspec@yahoogroups.com<br>
<b>Subject:</b> [MPEG-OTSPEC] AHG Kick-off - new email list, new mandates! IMPORTANT!<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear members of the AHG on Font Format,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As Heraclitus once said, “The only constant in life is change”, and this group is no exception!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You may have seen multiple Yahoo Groups notifications that they have removed all user-generated content from their servers. Since we’ve been using Yahoo Groups as our AHG host for over twelve years, we’ve enjoyed many good features they
used to offer – most notable for this AHG were web archive of our emails and file storage facilities, which are now gone. Hence, we decided to transition to a more user-friendly environment and Christian Timmerer (who is a long-time email list host for all
of MPEG) has graciously agreed to setup and host a new email list and also host the public email archive. Thank you Christian for all your help and hard work, and for making it easier to transition from one email list host to another!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Speaking about new email list and new email list archive – we’ve been able to preserve most [but not all] of the messages stored in the Yahoo Groups email archive, and transferred them to the new list. The archive is publicly available
via this URL: <a href="https://protect-us.mimecast.com/s/GTCJCqxr5lFBj22FZ7xaZ">
https://lists.aau.at/pipermail/mpeg-otspec/</a><o:p></o:p></p>
<p class="MsoNormal">(A file containing small portion of the Yahoo Groups emails was corrupted and it looks like some of the old messages are now malformed and recorded as “January 2020” communications, which is obviously not the case. I hope we didn’t lose
much because of it, but the major portions of the old archive are preserved.) Please note that since the email list archive is public (as used to be the case with Yahoo archive), any email message sent to the AHG list can be seen by anyone outside this group.
This is a very convenient feature if/when we need to share the information and invite outside experts to contribute to our work, but please keep this in mind and make sure that you do not include any information in our email communications that is not intended
to be seen by general public. As it used to be the case, one needs to be a registered AHG list member to be able to send emails to the AHG email list, but the email archive can be seen by anyone!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All subscribers of the Yahoo Group list have been automatically re-subscribed to the new list, you should have received email notification about it. IMPORTANT – please note that the subscription notification email also contained a password
automatically generated for you! You can change the password for something that is easier to remember but please DO NOT reuse any of the important/valuable passwords – the email list server will send you a reminder once a month about your active subscription
status, and those reminders WILL include your password in CLEARTEXT, which is not a secure form of communication. For new members who wish to subscribe, or to change your subscription preferences, or to unsubscribe - please visit:
<a href="https://protect-us.mimecast.com/s/3Ma0Crkv5mtMlmmSzbWtI">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><o:p></o:p></p>
<p class="MsoNormal">Last but not least, this message is addressed to both old and new email lists; going forward we will only be using the new email list address:
<a href="mailto:mpeg-otspec@lists.aau.at"><span style="font-size:13.5pt;background:white">mpeg-otspec@lists.aau.at</span></a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">New AHG Mandate!<o:p></o:p></p>
<p class="MsoNormal">At the last WG11 (MPEG) meeting in January, we received liaison statements from SC34 (available as input contribution m52545) and from W3C CSS Working Group (m52854, also available at
<a href="https://protect-us.mimecast.com/s/1zipCv2z58h1zllHzmAH9">https://lists.w3.org/Archives/Public/www-archive/2020Feb/att-0005/CSS-SC29-20200113.pdf</a>) where they identified certain technical issues (see Annex A of the CSS liaison) that may necessitate
further changes to the OFF specification. Our mandate [until the next MPEG meeting] is to:<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. To study the technical issues outlined in the liaison statements from SC34 (m52545) and from CSS WG (m52854)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. Identify possible approaches to solving confirmed technical issues, and communicate with the members of CSS WG to discuss and resolve any identified ambiguities that need
clarifications, or requirements for new features and technology to support new functionality.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">3. Develop and propose to WG11 input contributions that would become the basis for a new work item, and suggest a way forward.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Welcome to the new(-ish) AHG on Font Format!<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>