2013/4/8 David Turner <[email protected]> > > > 2013/3/27 Werner LEMBERG <[email protected]> > >> >> > 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 OSX Chrome specifically does different to other >> > browsers, and i will report it there too. >> >> Chrome uses FreeType, right? In case this is true, I really wonder >> what's going on... >> >> Chrome doesn't necessarily use FreeType, it depends on the platform. More > specifically, it uses the Skia library that has several 'font host' > implementations depending on the platform it runs on. On OS X, I believe it > uses platform-specific APIs to render text / glyphs. >
David right. On Mac OS X, FreeType is not used by Chrome/Skia afaik. > > >> > How can i best help you with this? i have a mac and use Chrome :-/ >> >> Thanks for your offer. I think we need assistance from the Chrome >> developers. Is there a bug report already for this issue? >> >> >> Werner >> >> _______________________________________________ >> Freetype-devel mailing list >> [email protected] >> https://lists.nongnu.org/mailman/listinfo/freetype-devel >> > > > _______________________________________________ > Freetype-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/freetype-devel > >
_______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
