<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=utf-8">
<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-family:"Calibri",sans-serif;}
@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">Folks,<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">In order to maintain the clarity of the discussion, I’d like to make sure we are clear about certain aspects of standardization process, especially when it relates
to words we use to identify / label our activities. I think this would be useful for those folks in particular who have not had much of “formal” standards development experience, and for whom the terminology and the overloaded meaning of it could be a bit
elusive.<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">The “working group” concept has different meaning to different people. For example, in the context of W3C, the Working Group is setup with clearly defined scope
and a set of deliverables. These goals are defined by the formal document called the charter of the W3C WG, which has to be approved by the W3C Advisory Committee before the group is launched, and once the WG has accomplished its stated goals it is either
disbanded or re-chartered, depending on the scope of work and future plans. In the context of ISO, the Working Group is a structural unit, an entity that is a backbone of the corresponding ISO Subcommittee, and is usually setup to fulfill the standardization
needs in the particular field that may (but is not required to) span multiple industries, develop multiple different standards, and is expected to run over fairly lengthy timeline. E.g., JPEG and MPEG activities used to be setup as ISO Working Groups [of our
Subcommittee #29), with JPEG continuing as the WG, and MPEG now been split into multiple connected Working Groups due to its wide industry scope and reach. I am not familiar with the details of the Unicode Consortium organizational structure, but I suspect
that the UTC itself is close in its scope to what would’ve been a WG in ISO organization.
<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">TL;DR: a “working group” term may simply mean a venue where things get done for some of us, and it may be seen as a BIG DEAL for others, depending on their prior
experiences. This particular Ad-Hoc Group [on Font Format] is a unit of ISO Working Group where things get done – this is exactly the place where technical solutions are discussed and a consensus decision can be reached – but our “output” are proposals and
expert recommendations to the ISO WG, the rest is happening there according to ISO Directives / process / policies.<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">I am sure it is our collective goal that the text shaping / layout discussions will provide us with necessary details to precisely define the scope of this activity
and decide on how to formalize it in the best interests of the whole industry (and I don’t just mean us, I mean the users of the technology we will have developed, which is literally every living being who speaks and writes!)<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">To answer Murata-san’s question – most of the issues the CSS WG raised are directly related to the current font format activity. Some of them need further analysis
and discussions, some (‘vert’ feature) have been recently addressed in the latest amendment (and may still need further discussions), some of them (cursive elongation) may not need any further development and may benefit from the already existing technical
solutions (such as e.g. “JSTF – Justification Table”), but it is definitely within a scope of the _<i>established</i>_ AHG activities.<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">Hoping that you will find these explanations useful,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Vladimir<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> mpeg-otspec <mpeg-otspec-bounces@lists.aau.at>
<b>On Behalf Of </b>MURATA Makoto<br>
<b>Sent:</b> Wednesday, August 12, 2020 5:36 AM<br>
<b>To:</b> mpeg-otspec@lists.aau.at<br>
<b>Subject:</b> [MPEG-OTSPEC] Issues from CSS: Will they be covered by the text shaping WG?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">The CSS WG of W3C raised 9 issues<br>
about interactions of OpenType and CSS<br>
in their liaison statement to SC29 WG11, <br>
available at <a href="https://protect-us.mimecast.com/s/wZ1VCER2v0u37w5psNMhUz">https://lists.w3.org/Archives/Public/www-archive/2020Feb/att-0005/CSS-SC29-20200113.pdf</a>)<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
Are they in the scope of the text shaping WG?<br>
<br>
1. Lack of font metrics for writing systems other than Western &<br>
2. Italic / Oblique Default Angle<br>
3. Compatibility problem with 'vert'<br>
4. Clarifications for 'vert'<br>
5. Clarifications for Bopomofo<br>
6. Cursive elongation<br>
7. Fidelity of Font Metrics<br>
8. Required vs Optional Ligatures<br>
9. Overline Metrics<br>
<br>
<br>
-- <br>
Regards,<br>
Makoto<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>