<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:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
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.EmailStyle18
{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;}
--></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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dear Suzuki-san,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thank you for your comments. Please see my responses below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">On Wednesday, October 7, 2020 5:01 AM suzuki toshiya wrote:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
> The AHG conducted numerous discussions that touched on many aspects of extending our work into the new technical areas.
<br>
<br>
> We considered a broad range of approaches and possible solutions that operate on and at the interface between text encoding and font format, including both general and specific aspects of standardization work that may not necessarily fall under the SC29/WG3
umbrella. <br>
<br>
Because there is a description "new technical areas", I hope more detailed comment for "not that may not necessarily fall under the SC29/WG3 umbrella". Is it technical mismatch (e.g. a part of ISO/IEC 14496 is inappropriate), or, organizational/procedual mismatch?
(e.g. ISO style development is inappropriate).<br>
<br>
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">As you know, the Font and Text CG was created under the W3C umbrella to explore new work items related to text layout and shaping, as well as anything else that
may fall between text encoding and font format specification. The work of this CG will most likely produce new specifications related to this areas, as well as new proposals to extend font format specification. Some topics [such as script-specific shaping
specifications] may be adjacent, but not directly related to font format, and the new spec may be produced elsewhere (either W3C or Unicode, as the CG decides), other topics such as extending glyph IDs fields to overcome 64K limit are directly related to OFF
but require significant, wider community effort, and the results of this work is expected to be offered as an input to SC29/WG3.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
The proposal to extend the font file format of ISO/IEC 14496-22, like, LABL table extension proposed by Adam, is still appropriate to be discussed under SC29/WG3 umbrella, without waiting for the formation of the technical group under W3C? I think, Font AHG
is keep the motivation to maintain the font file format spec, and not leave it to W3C's technical group.<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Yes, the AHG is still an appropriate venue to present and discuss any proposals to extend ISO/IEC 14496-22, and the standard development will continue under SC29/WG3.
There are no dependencies between the two groups and both of them operate freely and independently.<o:p></o:p></span></p>
<p class="MsoNormal"><br>
<span style="color:#1F497D">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Vlad<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>