<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Behdad, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is not a case of whether to _<i>add</i>_ something to OFF; you’re proposing _<i>removing</i>_ something that’s been part of OFF since the first edition. Given that, and given that CFF(2) is supported in several platforms and products,
this has the appearance of objecting to CFF for the sake of objecting. What problem, exactly, are you trying to solve?<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> mpeg-otspec <mpeg-otspec-bounces@lists.aau.at> <b>
On Behalf Of </b>Behdad Esfahbod<br>
<b>Sent:</b> Thursday, October 8, 2020 8:57 AM<br>
<b>To:</b> Dave Crossland <dcrossland@google.com><br>
<b>Cc:</b> mpeg-otspec <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> Re: [MPEG-OTSPEC] Removal of the CFF and CF2 from OFF standard (was: Proposal to make OFF complete)<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">You seem more focused on objecting than to reason about my proposal or why your objection is legitimate. You did NOT even reply to the main issue:<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">> Sooooooo either CFF/CFF2 should be removed, *or* it be added as a work item that CFF/CFF2 hinting be documented as part of OFF.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#500050"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#500050">> Separately part of the same proposal was to document script-shaping as part of OFF; so I expect that to be added as a new work item proposal as well.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#500050"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal">behdad<br>
<a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbehdad.org%2F&data=04%7C01%7C%7Cce38ca89ba3c41760fcd08d86ba2fbbf%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637377695036156319%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Uij6kW3tYMVQhRNBbHq7piU3RhM7macKTlKXZHJvioQ%3D&reserved=0" target="_blank">http://behdad.org/</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Oct 7, 2020 at 5:13 PM Dave Crossland <<a href="mailto:dcrossland@google.com">dcrossland@google.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Oct 7, 2020, 6:55 PM Behdad Esfahbod <<a href="mailto:behdad@behdad.org" target="_blank">behdad@behdad.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">On Wed, Oct 7, 2020 at 4:48 PM Dave Crossland <<a href="mailto:dcrossland@google.com" target="_blank">dcrossland@google.com</a>> wrote:<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">
<div>
<div>
<div>
<p class="MsoNormal">On Wed, Oct 7, 2020 at 6:45 PM Behdad Esfahbod <<a href="mailto:behdad@behdad.org" target="_blank">behdad@behdad.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<p class="MsoNormal">On Wed, Oct 7, 2020 at 4:37 PM Dave Crossland <<a href="mailto:dcrossland@google.com" target="_blank">dcrossland@google.com</a>> wrote:<o:p></o:p></p>
</div>
</div>
</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">
<div>
<div>
<div>
<p class="MsoNormal">On Wed, Oct 7, 2020 at 5:51 PM Behdad Esfahbod <<a href="mailto:behdad@behdad.org" target="_blank">behdad@behdad.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">On Wed, Oct 7, 2020 at 3:35 PM Levantovsky, Vladimir <<a href="mailto:Vladimir.Levantovsky@monotype.com" target="_blank">Vladimir.Levantovsky@monotype.com</a>> wrote:<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">
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt">On Wednesday, August 19, 2020 12:40 AM Behdad Esfahbod wrote:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Moreover, I suggest CFF and CFF2 be removed from OFF. The claim-to-superiority of CFF format is: 1. better hinting, and 2. better compression. Re better-hinting, the interpretation of CFF hints is NOT specified anywhere. Adobe's code in FreeType is what we
have. Re better compression, the existence of CFF in OpenType / OFF is partly why adding quadratic beziers to glyf table has continually not happened.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
In reality, CFF only serves Adobe, who sells their rasterizer to MS / Apple platforms and serves only Adobe. Another example of Adobe abusing the "open" ideology / terminology is the Noto CJK / Adobe-equivalent. It's NOT open-source by any means. The sources
are not available. That's something that I pointed out directly to Ken Lunde at one of his Unicode Conference presentations. Adobe is clearly aware of it. And I couldn't fix when I was at Google.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Rip the bandaid. Make open standards truly open.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">With my SC29/WG3 member representative hat on (and _<i>not</i>_ serving in my capacity as a chair of this AHG) I object to this proposal. With many thousands
of fonts currently deployed, and at least two (or more) different implementations available – this proposal, if considered, would do more harm than good.</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Okay let me narrow down the proposal to removing CFF2 only.<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I object to the proposal to remove CFF2, because while few CFF2 VF fonts are available, CFF2 is now widely implemented by font engines<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It's in OpenType. I don't see why it needs to be in OFF from a forward-looking point of view.<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">CFF2 needs to be in OFF because then it is definitively clear of rightholder friction, allowing it to be widely adopted. <o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">No one has suggested *why* it needs to be widely adopted. You can't just say "no". I argued that OFF is *incomplete* currently.<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Vlad brought up the counter argument that much existing usage depends on CFF being in OFF. You accepted this but then argue that not many cff2 fonts exist compared to cff1, or to TTF VF. But I don't think this is relevant, because fonts
themselves are only one piece of the puzzle. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<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">
<div>
<div>
<div>
<p class="MsoNormal">Sooooooo either CFF/CFF2 should be removed, *or* it be added as a work item that CFF/CFF2 hinting be documented as part of OFF.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Separately part of the same proposal was to document script-shaping as part of OFF; so I expect that to be added as a new work item proposal as well.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal">The many users of harfbuzz, that you tout, are doing so because OFF has cleared a path for that adoption. <o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I don't see how that argument holds. HarfBuzz implements ...<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It's an argument about adoption, not implementation.<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>