> After a bit of testing, I think I know where the glitches come from.
> They are usually digits (0, 2, 8), overshoots (C) or other parts
> (lower belly of R, see the last two comparison shots) being snapped
> to 1 pixel above where they should be. Emboldening probably lands
> the top of the stem
Dear Albert,
As
http://www.microsoft.com/typography/otspec/otff.htm#otttables
says, hmtx is "required" table for self standing font.
Also
https://partners.adobe.com/public/developer/en/font/5012.Type42_Spec.pdf
says, hmtx is "required" table for Type42 embedded font in
PostScript, and it is also
>> (this is tracing data from the current FreeType git version).
>
> So you're saying we should try to load some other substitute font if
> we encounter the font that i sent in the first email, right?
Yes, since the font is broken and can't be sanitized by FreeType.
Werner
___
On Sat, Sep 19, 2015 at 3:32 AM, Werner LEMBERG wrote:
> Are there any rendering differences to the old code?
There are not supposed to be any visible differences, assuming that
there are no bugs in either version.
On Sun, Sep 20, 2015 at 11:49 AM, Nikolaus Waxweiler wrote:
> Anything specific
I've been using the patch since yesterday and spotted no anomalies so
far in my daily routine. Anything specific to look for?
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
After a bit of testing, I think I know where the glitches come from.
They are usually digits (0, 2, 8), overshoots (C) or other parts (lower
belly of R, see the last two comparison shots) being snapped to 1 pixel
above where they should be. Emboldening probably lands the top of the
stems outsid
