<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 14 (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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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";
color:black;}
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
{mso-style-priority:99;
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";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
p.imprintuniqueid, li.imprintuniqueid, div.imprintuniqueid
{mso-style-name:imprintuniqueid;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle23
{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 bgcolor="white" 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">Hi Dave, all,<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">How are you? Just wanted to remind you that the next WG11 (MPEG) meeting will take place April 3-7 and we have until March 28 to finalize and submit an input
contribution with the proposed changes. Process-wise, it would be great if the input contribution is submitted as a result of the email discussion on the AHG list (<a href="mailto:mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a>) – when you think
you are ready to propose an updated text to address the lsb issue I can kick-start the discussion by simply forwarding Werner’s original email to the list.<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">Also, I’d really appreciate if you could find a time to review the updated Working Draft text of the OFF (sent to the AHG list, see
<a href="https://groups.yahoo.com/neo/groups/mpeg-OTspec/conversations/messages/1575">
https://groups.yahoo.com/neo/groups/mpeg-OTspec/conversations/messages/1575</a>) and submit your comments via email list as well.<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,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Vlad<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>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> Dave Arnold [mailto:darnold@adobe.com]
<br>
<b>Sent:</b> Friday, February 10, 2017 6:30 PM<br>
<b>To:</b> Levantovsky, Vladimir<br>
<b>Cc:</b> Peter Constable (petercon@microsoft.com); Read Roberts<br>
<b>Subject:</b> Re: [OpenType] CFF2 and lsb<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid white 1.0pt;padding:3.0pt 0in 0in 0in">
<p><span style="font-family:"Calibri","sans-serif"">Hi Vlad,</span><o:p></o:p></p>
<p><span style="font-family:"Calibri","sans-serif"">I've been able to discuss this only briefly with colleagues at Adobe. There are some aspects of LSB, both for variable fonts and for non-variable fonts, that we feel will require further discussion and it
does not seem appropriate to delay your submission now. So, we have no changes to propose for this round.</span><o:p></o:p></p>
<p><span style="font-family:"Calibri","sans-serif"">Peter, on the variable font aspects, I already noted that we concluded LSBmapping was not useful for CFF2. But I was struggling to explain why the situation was different for TT. One issue that concerns us
is the non-linearity of Min/Max and the difficulty of relying on interpolation to compute LSB for variable fonts. I'd like to discuss this with you before proposing wording for the spec.</span><o:p></o:p></p>
<p><span style="font-family:"Calibri","sans-serif"">Thanks.</span><o:p></o:p></p>
<p><span style="font-family:"Calibri","sans-serif"">-Dave</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 2/10/2017 9:24 AM, Levantovsky, Vladimir wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Off-list<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Hi Dave,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I wanted to follow up on the email exchange on OpenType list regarding spec clarifications. We are approaching the deadline for submission of the updated working draft OFF, and it would be an excellent opportunity to include some additional statements into the spec, before it is made available for public review. <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I can drag my feet a little longer if you think you can suggest some additional language soon, please let me know if you think it is feasible to add some new CFF2-related requirements and/or recommendations at this time.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thank you,<o:p></o:p></pre>
<pre>Vlad<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: <a href="mailto:listmaster@indx.co.uk">listmaster@indx.co.uk</a> [<a href="mailto:listmaster@indx.co.uk">mailto:listmaster@indx.co.uk</a>] On Behalf Of Peter Constable <o:p></o:p></pre>
<pre>Sent: Wednesday, February 08, 2017 11:49 AM<o:p></o:p></pre>
<pre>To: <a href="mailto:listmaster@indx.co.uk">listmaster@indx.co.uk</a><o:p></o:p></pre>
<pre>Subject: RE: [OpenType] CFF2 and lsb<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Message from OpenType list:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Dave, can you suggest some statements for requirements or recommendations, and which chapter you think they belong.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks<o:p></o:p></pre>
<pre>Peter<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: <a href="mailto:listmaster@indx.co.uk">listmaster@indx.co.uk</a> [<a href="mailto:listmaster@indx.co.uk">mailto:listmaster@indx.co.uk</a>] On Behalf Of Dave Arnold<o:p></o:p></pre>
<pre>Sent: Tuesday, February 7, 2017 1:13 PM<o:p></o:p></pre>
<pre>To: <a href="mailto:listmaster@indx.co.uk">listmaster@indx.co.uk</a><o:p></o:p></pre>
<pre>Subject: Re: [OpenType] CFF2 and lsb<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Message from OpenType list:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>****** Attachments to this email message have been removed ******<o:p></o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Hi Werner,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Adobe builds CFF fonts with head.flags bit 1 set and with lsb in the hmtx table set to xMin. As with the hmtx advance width, the lsb is informational only; its value is not used in rendering.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>For CFF2, hmtx should be built the same way, using the default instance.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>For CFF2, lsb in HVAR is not useful, so an LSBmapping table is not provided..<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I agree the spec could be clarified on these points.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-Dave<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>________________________________<o:p></o:p></pre>
<pre>From: <a href="mailto:listmaster@indx.co.uk">listmaster@indx.co.uk</a> <a href="mailto:listmaster@indx.co.uk"><listmaster@indx.co.uk></a> on behalf of Werner LEMBERG <a href="mailto:werner@lemberg.at"><werner@lemberg.at></a><o:p></o:p></pre>
<pre>Sent: Monday, February 6, 2017 10:08:28 PM<o:p></o:p></pre>
<pre>To: <a href="mailto:listmaster@indx.co.uk">listmaster@indx.co.uk</a><o:p></o:p></pre>
<pre>Subject: Re: [OpenType] CFF2 and lsb<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Message from OpenType list:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>In non-variable fonts, bit 1 of head.flags is used to indicate whether <o:p></o:p></pre>
<pre>or not lsb = xMin (lsb point at x = 0). That flag pertains to <o:p></o:p></pre>
<pre>TrueType outlines only.<o:p></o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre>Thanks.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Adobe folk — or someone who understands CFF(2) better than me — can <o:p></o:p></pre>
<pre>clarify the CFF question.<o:p></o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre>It's basically the question how CFF and CFF2 is integrated into the SFNT format. My gut feeling is that bit 1 is always set for CFF and CFF2, but it would be nice have something in the specs that clarifies the issue.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre> Werner<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>List archive: <a href="http://www.indx.co.uk/biglistarchive/">http://www.indx.co.uk/biglistarchive/</a><o:p></o:p></pre>
<pre>List settings: <a href="http://www.indx.co.uk/biglistarchive/?mode=usersettings">http://www.indx.co.uk/biglistarchive/?mode=usersettings</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>subscribe: <a href="mailto:opentype-subscribe@indx.co.uk">opentype-subscribe@indx.co.uk</a><o:p></o:p></pre>
<pre>unsubscribe: <a href="mailto:opentype-unsubscribe@indx.co.uk">opentype-unsubscribe@indx.co.uk</a><o:p></o:p></pre>
<pre>messages: <a href="mailto:opentype-list@indx.co.uk">opentype-list@indx.co.uk</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>****** Attachments to this email message have been removed ******<o:p></o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>List archive: <a href="http://www.indx.co.uk/biglistarchive/">http://www.indx.co.uk/biglistarchive/</a><o:p></o:p></pre>
<pre>List settings: <a href="http://www.indx.co.uk/biglistarchive/?mode=usersettings">http://www.indx.co.uk/biglistarchive/?mode=usersettings</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>subscribe: <a href="mailto:opentype-subscribe@indx.co.uk">opentype-subscribe@indx.co.uk</a><o:p></o:p></pre>
<pre>unsubscribe: <a href="mailto:opentype-unsubscribe@indx.co.uk">opentype-unsubscribe@indx.co.uk</a><o:p></o:p></pre>
<pre>messages: <a href="mailto:opentype-list@indx.co.uk">opentype-list@indx.co.uk</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>List archive: <a href="http://www.indx.co.uk/biglistarchive/">http://www.indx.co.uk/biglistarchive/</a><o:p></o:p></pre>
<pre>List settings: <a href="http://www.indx.co.uk/biglistarchive/?mode=usersettings">http://www.indx.co.uk/biglistarchive/?mode=usersettings</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>subscribe: <a href="mailto:opentype-subscribe@indx.co.uk">opentype-subscribe@indx.co.uk</a><o:p></o:p></pre>
<pre>unsubscribe: <a href="mailto:opentype-unsubscribe@indx.co.uk">opentype-unsubscribe@indx.co.uk</a><o:p></o:p></pre>
<pre>messages: <a href="mailto:opentype-list@indx.co.uk">opentype-list@indx.co.uk</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>