Re: [ft-devel] ttfautohint - render issue with composites on OSX CHrome
2013/3/27 Werner LEMBERG w...@gnu.org 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. 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 Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ttfautohint - render issue with composites on OSX CHrome
2013/4/8 David Turner da...@freetype.org 2013/3/27 Werner LEMBERG w...@gnu.org 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 Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ttfautohint - render issue with composites on OSX CHrome
2013/3/27 Vernon Adams v...@newtypography.co.uk
test page at http://vernnobile.github.com/cloud-fonts.com/garamond.html
Thank you for the link. I was able to reproduce the problem and filed a
bug at http://crbug.com/229010.
BTW, why would like to serve a font with hint instruction to OS X? OS X
will not utilize the hint instructions.
Jungshik
-v
On 27 Mar 2013, at 12:09, Jungshik Shin (신정식, 申政湜) jungs...@google.com
wrote:
Hi Vernon,
It'll be great if you set up a test page so that Skia team can play with
it if there's still an issue.
Thank you,
Jungshik
2013/3/27 Vernon Adams v...@newtypography.co.uk
Hi
I think the designer of the font actually found a 'work around' when
generating the fonts, so the page is rendering ok now. The 'work around' is
not an ideal solution though. I will test some more and see if the original
issue is still occurring. I will set up a test page too.
Many thanks
-vernon
On 27 Mar 2013, at 11:00, Jungshik Shin (신정식, 申政湜) jungs...@google.com
wrote:
Having said that, I've tried your web page with Chrome 26.0.1410.5 dev
channel and I don't see any problem ('i', 'ff' and 'f'). I may have missed
what you see and I'm attaching a screenshot for you to take a look at. I
also tried Chrome canary (nightly build) 27.0.1454.0 and didn't see any
problem, either.
It's possible that Skia had a problem with fonts auto-hinted by
ttautohint, but the issue has been fixed since. What version of Chrome do
you have?
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
