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 _______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
