<html 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;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Adobe objects to the proposal to remove CFF and CFF2, as well. Every major implementer of OpenType supports CFF and CFF2, the former for sometimes decades, the latter for up to several years.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CFF is part of the PDF specification (ISO 32000-1) and CFF fonts are widely used, as well as bundled in places such as MacOS (the Hiragino family, for example). CFF2 is the forward-looking version of CFF, one that supports variability as
well as non-variability. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CFF and CFF2 have important facilities not available elsewhere in OT, most importantly cubic Beziers and the PostScript approach to hinting. (Eric Muller & Terry Dowling have responded more on this email list on the rationale and merits
of CFF hinting.)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CFF2, in addition, supports 32-bit glyph IDs, an important future-looking facility that is being discussed currently (<a href="https://github.com/MPEGGroup/OpenFontFormat/issues/10">https://github.com/MPEGGroup/OpenFontFormat/issues/10</a>).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The compression benefits of CFF2 are substantial, and in large fonts such as the pan-CJK family we’re working on, the compression is quite significant.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We hadn’t responded earlier since this was first presented as a “suggestion”, and since extensive discussion around hinting has since happened. (Also, the rasterizer code is not proprietary; Adobe freely shared the code with FreeType and
Microsoft, and Apple implemented their own.)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">mpeg-otspec <mpeg-otspec-bounces@lists.aau.at> on behalf of Behdad Esfahbod <behdad@behdad.org><br>
<b>Date: </b>Wednesday, October 7, 2020 at 5:51 PM<br>
<b>To: </b>"Levantovsky, Vladimir" <Vladimir.Levantovsky@monotype.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></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">On Wed, Oct 7, 2020 at 3:35 PM Levantovsky, Vladimir <<a href="mailto:Vladimir.Levantovsky@monotype.com">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>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Is there any evidence that there are "thousands of fonts currently deployed"? And is there any evidence of at least two different implementations (that is, that are not derived from same Adobe implementation)?<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>
<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;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Vlad</span><o:p></o:p></p>
<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"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">behdad<br>
<a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect-us.mimecast.com%2Fs%2Fos4aC68vyBsrBZ6ycpkuzx%2F&data=02%7C01%7Crhatigan%40adobe.com%7C2c0843fa1ecd4291a7e508d86b0b2755%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637377042944115147&sdata=mIrCWQAVg%2Fvwk9e5%2F6X%2FfiFa2%2BEkM8s8ED0hSBwGJhs%3D&reserved=0" target="_blank">http://behdad.org/</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>