<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - PDF Text hinting does not work for embedded otf fonts (CID Type 0C), does work for truetype." href="https://bugs.freedesktop.org/show_bug.cgi?id=78990#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - PDF Text hinting does not work for embedded otf fonts (CID Type 0C), does work for truetype." href="https://bugs.freedesktop.org/show_bug.cgi?id=78990">bug 78990</a> from <a class="email" href="mailto:cloos@jhcloos.com" title="James Cloos <cloos@jhcloos.com>"> James Cloos</a> <pre>> I've uploaded a corrected PDF as there was a mixup with the fonts I used > for the example. I’m interacting with bz via email, and missed the additional comments, including that update, when I first replied. Appologies. b> In brief, the two fonts should render identically, and do when zoomed b> in close enough. There is no such thing as identical hinting between CFF and glyf fonts. How did you generate the instructions for the glyf (aka ttf)? Fontforge? Ttfautohint? By hand? I see that the metrics are different. Did you lose kerning? I expect a pdf viewer to disable all hinting for the rendered page. AFAIK evince follows that philosophy. But if not, freetype added a new hinting engine in that last year, contributed by Adobe, which darkens glyphs at low resolutions. Perhaps that explains what you see? Or, the difference between how cubic and quadratic splines render might be noticible at those p/ex sizes.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>