About that Freetype2 update
Joe Marcus Clarke
marcus at FreeBSD.org
Tue Sep 30 01:22:23 PDT 2003
On Tue, 2003-09-30 at 04:15, Michael Collette wrote:
> The Freetype2 port itself worked quite nicely. Upgraded properly, no compile
> problems. I had been looking forward to seeing this get updated due to some
> visual problems with Scribus.
> Long story short, I uninstalled the new version and added the old one back in
> via a package. All of my TrueType fonts here got real jaggedy. They were
> readable, but the quality was seriously degraded.
> I run with a KDE desktop and no anti-aliasing, as this is a laptop. AA on an
> LCD screen just looks fuzzy. I should note that with AA turned on, the new
> Freetype2 does just fine. The not so subtle difference is when there isn't
> any AA help.
> I should also note that this was certainly no fix for Scribus. With the
> updated version of Freetype2 I wasn't able to even see any True Type fonts at
> Without doing any real investigative work, I'm leaning to one of three
> explanations here...
> 1. Something is goofy in this new version of Freetype2
> 2. Freetype2 reall wanted that byte code interpreter after all
> 3. I need to recompile the applications that depend on Freetype2
> No major crisis here, as the old version seems to still be doing just fine.
> Thought I'd pass along what all I saw with this new one just the same.
Everything here looks beautiful. You're free to test your assumptions
above. If the byte-code interpreter helps, I can always add that back
in as an option.
> Later on,
Joe Marcus Clarke
FreeBSD GNOME Team :: gnome at FreeBSD.org
FreeNode / #freebsd-gnome
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20030930/fcea66fd/attachment.bin
More information about the freebsd-ports