2013/4/10 Dave Crossland <[email protected]>

> On 11 April 2013 00:54, Jungshik Shin (신정식, 申政湜) <[email protected]>
> wrote:
> >
> > the issue appears to be in fontforge
>
> I've started a ff bug for this at
> https://github.com/fontforge/fontforge/issues/528


Thank you for the bug report, but I'm afraid your bug description has
misleading bits:

* and this causes issues with freetype and therefore browsers that use
freetype, like Chromium.*
*
*
Chrome on Mac OS X does NOT use FreeType as David Turner wrote earlier.
Please, read https://code.google.com/p/chromium/issues/detail?id=229010#c1
: FreeType does not have a problem with this, but Skia on Mac OS X does
have a problem because it relieds on CTFontGetBoundingRectsForGlyphs.

Jungshik
_______________________________________________
Freetype-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Reply via email to