On 4/9/07, Tijnema ! <[EMAIL PROTECTED]> wrote: > On 4/9/07, Peter Keller <[EMAIL PROTECTED]> wrote: > > On Mon, 09 Apr 2007 19:47:06 Fix wrote: > > > On 4/9/07, Lauri Kasanen <[EMAIL PROTECTED]> wrote: > > > > This was discussed a while ago. It is a bug in freetype: The book > > > > advises > > > > to use a sed command to enable bytecode interpreter, but that is broken > > > > in that version and causes fonts looking like that... > > > > > > What versions are broken? I use freetype-2.3.2, not 2.1.10 as in the book. > > > > I think you should probably downgrade to 2.1.10. See > > http://freetype.sourceforge.net/freetype2/freetype-2.2.0.html > > What do the more knowledgeable among us say? > > I think you should upgrade to freetype-2.3.3, it has just been > released with a set of bug fixes, and i thought it fixes this problem > too.
I say upgrade to 2.3.3 and add some information to our ticket to make things easy on me :) http://wiki.linuxfromscratch.org/blfs/ticket/1988 Here's the announcement for 2.3.3, and it does indeed have some fixes for the bytecode interpreter. http://lists.nongnu.org/archive/html/freetype-announce/2007-04/msg00000.html -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page