freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ft-devel] ttfautohint - render issue with composites on OSX CHrome


From: Vernon Adams
Subject: [ft-devel] ttfautohint - render issue with composites on OSX CHrome
Date: Tue, 26 Mar 2013 11:06:25 -0700

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 to above is using different gsub tables for substituting the 
'f' with a 'longs' , 'i' with 'dotless i' + 'dot accent', 'f', 'f' pairs with 
'ff' ligature etc. 

The fonts are autohinted with the 'hint composites' option selected, and the 
effected glyphs contain the ttfautohint dummy glyph used when autohinting 
composites.

Please note it is only Chrome on OSX that shows this messed up rendering, other 
browsers on OSX render the glyphs fine.

-v


reply via email to

[Prev in Thread] Current Thread [Next in Thread]