There appears to be a OSX Chrome render issue with specific glyphs auto
instructed with ttfautohint.
Please see http://www.georgduffner.at/ebgaramond/
On OSX Chrome all characters that are composite substitute glyphs are being
rendered badly (part wiped out, missing stems etc)
The site linked
On Tue, Mar 26, 2013 at 2:06 PM, Vernon Adams v...@newtypography.co.ukwrote:
Please note it is only Chrome on OSX that shows this messed up rendering,
other browsers on OSX render the glyphs fine.
Why do you think this is FreeType problem then? You really need to
reproduce the problem with
Isn't the freetype-devel list still used as the ttfautohint-devel list?
Apologies if that's not the case, but i simply replied to the ft-devel post
'[ft] ttfautohint 0.95 has been released' from 8th March to post this issue.
-v
On 26 Mar 2013, at 12:55, Alexei Podtelezhnikov
Isn't the freetype-devel list still used as the ttfautohint-devel
list?
Yes, it is.
Why do you think this is FreeType problem then? You really need to
reproduce the problem with more directly, e.g. using ftview. There
is this bug report http://savannah.nongnu.org/bugs/?33272 , which I
Werner,
It's an issue when ttfautohint is using dummy glyphs as a workaround for
hinting composite glyphs. Untill know it was assumed that it was a problem free
workaround. My report shows that it seems to be creating problems on OSX
Chrome. Of course it could be a bug caused by something that
