<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 10/7/2020 14:50, Behdad Esfahbod
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAF63+7WzGJrs70SvGvstB6gEwXYXomG9ARwJ6Dj6qJwrTrQdRw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Wed, Oct 7, 2020 at 3:35 PM Levantovsky,
          Vladimir <<a
            href="mailto:Vladimir.Levantovsky@monotype.com"
            moz-do-not-send="true">Vladimir.Levantovsky@monotype.com</a>>
          wrote:<br>
        </div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div lang="EN-US">
              <div class="gmail-m_-3630416044460682666WordSection1">
                <div>
                  <div>
                    <p class="MsoNormal"><span
                        style="font-size:11pt;font-family:Calibri,sans-serif">On
                        Wednesday, August 19, 2020 12:40 AM Behdad
                        Esfahbod wrote:<br>
                        <br>
                      </span></p>
                  </div>
                  <div>
                    <p class="MsoNormal" style="margin-left:0.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.</p>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p> This frequently repeated argument for the removal of CFF/CFF2 is
      lack of specification for how hints are used. <br>
    </p>
    <p>I'm confused by this because it seems quite clear that
      rasterization issues are not part of the MPEG-OTSPEC area of
      responsibility.</p>
    <br>
    <p>The same suggestion  could be made to remove TrueType
      instructions because they are completely ignored or interpreted in
      unspecified ways by major implementations. <br>
    </p>
    <p>I'm a retired rasterizer implementer with production code
      experience for both TrueType and CFF.  A skill clearly
      underrepresented in these discussions.<br>
    </p>
    <p> Terence Dowling<br>
    </p>
    <br>
    <p> P.S. It is worth noting that the hinting structure and general
      information philosophy was publicly documented in 1990 <br>
    </p>
    <p>see: <a class="moz-txt-link-freetext"
href="https://www.adobe.com/content/dam/acom/en/devnet/font/pdfs/T1_SPEC.pdf">https://www.adobe.com/content/dam/acom/en/devnet/font/pdfs/T1_SPEC.pdf</a>
      <br>
    </p>
    <p>It has been public for about 30 years.</p>
    <blockquote type="cite"
cite="mid:CAF63+7WzGJrs70SvGvstB6gEwXYXomG9ARwJ6Dj6qJwrTrQdRw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">mpeg-otspec mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>
<a class="moz-txt-link-freetext" href="https://lists.aau.at/mailman/listinfo/mpeg-otspec">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>