In freetype 2.2.1 CVS version from 20061013, "Luxi Mono" is
rendered completely broken when the autohinter is not used.

See this screen shot (from ftview):

http://lisa.goe.net/~mfabian/freetype2-luxi-mono-autohinting-problem/luxi-mono-autohinting-off-ft-2.2.1.20061013.png

When the autohinter is switched on, the problem disappears,
see the following screen shot:

http://lisa.goe.net/~mfabian/freetype2-luxi-mono-autohinting-problem/luxi-mono-autohinting-on-ft-2.2.1.20061013.png

It is nice that the autohinter improves the rendering, but why is the
rendering completely broken without the autohinter?

The problem did not exist in freetype 2.1.10, see the following
two screen shots:

http://lisa.goe.net/~mfabian/freetype2-luxi-mono-autohinting-problem/luxi-mono-autohinting-off-ft-2.1.10.png
http://lisa.goe.net/~mfabian/freetype2-luxi-mono-autohinting-problem/luxi-mono-autohinting-on-ft-2.1.10.png

In freetype 2.1.10, switching off the autohinter changes the rendering
results only slighly, there is no such huge difference as with
freetype 2.2.1.20061013 where the rendering of "Luxi Mono" without the
autohinter is completely broken.

By the way, both freetype version used for testing this were compiled
*with* the byte code interpreter!

The font is /usr/share/fonts/truetype/luximr.ttf as distributed
with X.org release 7.1. This font is also available here:

http://lisa.goe.net/~mfabian/freetype2-luxi-mono-autohinting-problem/luximr.ttf

-- 
Mike FABIAN   <[EMAIL PROTECTED]>   http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。


_______________________________________________
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

Reply via email to