<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:"Cordia New";
panose-1:2 11 3 4 2 2 2 2 2 4;}
@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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.gmaildefault
{mso-style-name:gmail_default;}
.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">I guess there’s another question I can ask: When using GPOS type 2 lookups for ‘kern’ (or ‘vkrn’, ‘chws’, ‘vchw’), do font developers / font development tools usually make adjustments to the first glyph only?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Per the currently spec’d processing, if valueFormat2 in GPOS type 2 lookups is 0, then the second glyph is not consumed. If that is typically the way kerning lookups are implemented (which seems reasonable), then indeed the intent of the
wording all along may have been a recommendation to font developers, not a requirement on shaping engine implementations — which is how it currently comes across (at least, to me). And if that is the intent, then I think the wording should be revised to make
that clear.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Koji Ishii <kojii@chromium.org> <br>
<b>Sent:</b> Wednesday, August 19, 2020 11:31 PM<br>
<b>To:</b> Ken Lunde <ken.lunde@gmail.com><br>
<b>Cc:</b> Peter Constable <pgcon6@msn.com>; MPEG OT Spec list (mpeg-otspec@lists.aau.at) <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> Re: [MPEG-OTSPEC] lookup processing and 'chws', 'vchw'<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">> On Aug 19, 2020, at 08:55, Peter Constable <<a href="mailto:pgcon6@msn.com" target="_blank">pgcon6@msn.com</a>> wrote:<br>
> <span class="gmaildefault"><span style="font-family:"Arial",sans-serif">:</span></span><br>
> So, the “not consume” clause in the description of ‘chws’ and ‘vchw’ would seem to be consistent with the rest of the spec _provided that the GPOS type 2 lookups do not act on the second glyph_. However, the descriptions for these features don’t give any
indication that that constraint should be followed.<br>
> <br>
> Thus, I’d like to know if such a constraint on type 2 lookups used for ‘chws’/’vchw’ was intended but somehow left out of the descriptions (hence should be added)? Or was it really intended (as it appears on the surface) that type 2 lookups for ‘chws’/’vchw’
should be allowed to act on the second glyph but that clients should _exceptionally_ not consume the second glyph in this case?<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Ken knows the text best but I think the answer is the former; there's no intention to add an exceptional behavior. The intention is to use existing code without modifications. Ken and I were
testing this feature using existing browsers:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><a href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkojiishi.github.io%2Fcspc%2Ftest.html&data=02%7C01%7C%7C82e2d555f0bd428da5ad08d844d2a574%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637335018787421525&sdata=ad7rwtAnH03qhHAEEilsFOFL5oXOHybxJq%2FNy2pTfco%3D&reserved=0">https://kojiishi.github.io/cspc/test.html</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>