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

[Vernon Adams]

Maybe fontforge is doing this but…

3 things;

1. The problematic glyphs were 'special' in that they had been through 
ttfautohint and hinted as 'composites'. Unhinted, or hinted but without the 
'composites' option, versions of same font had no problematic glyphs.
2. The problematic glyphs were 'special' in that they contained composites AND 
the .ttfautohint glyph.
3. Why does this issue only occur on OSX Chrome, and no other browser or 
browser/OS combo??

:)

-v


On 11 Apr 2013, at 00:54, Jungshik Shin (신정식, 申政湜) <address@hidden> wrote:

> The latest finding from http://crbug.com/229010 : 
> 
> As it turns out, I do have access to the original font, as it is available at 
> https://github.com/georgd/EB-Garamond . Very nice font, by the way. The font 
> is, in fact, 1000upem, and makefont.py (part of the build process for the 
> font) tells font forge to push the em to 2048. This seems to be the step 
> causing the issue, as ttfautohint is leaving all these values alone. As a 
> result, the issue appears to be in fontforge. There appear to have been 
> related issues in the past as well, see 
> http://sourceforge.net/mailarchive/forum.php?thread_name=1228364630.1432.0.camel%40lynch&forum_name=fontforge-devel
>  
> 
> Jungshik