On Mon, Dec 16, 2013 at 11:53:01AM +0100, BubuXP wrote: > I found the cause (maybe). > Probably the fuzzy fonts are all OpenType fonts. Starting from > freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for > those class of fonts. > https://blogs.adobe.com/typblography/2013/05/adobe-contributes-cff-rasterizer-to-freetype.html
Yes, this is the change that I suspected would be the source of the problem. I just haven't had time yet to set up an environment where I could reproduce it to confirm. Use of the Adobe hinter is optional and the default can be changed at compile time. Does someone who's hitting this bug want to try rebuilding freetype locally with the option changed, to see if that fixes it? (If not, I'll prepare a test build for people to try, but it'll take a few days before I can get to it.) > From: > http://lists.freedesktop.org/archives/fontconfig/2013-December/005026.html > > If I remember correctly the new Adobe CFF hinter hinting levels are out of > > sync with the autohinter used with TTF fonts. > > As reported in the above link, to mitigate the bug this fix should be > enabled by default in the next fontconfig version (2.11.1, that will > be released soon): > > <match target="font"> > <test name="fontformat" compare="eq"> > <string>CFF</string> > </test> > <edit name="hintstyle" mode="assign"> > <const>hintslight</const> > </edit> > </match> > -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
