On Tuesday 03 December 2002 17:12, Karol Pietrzak wrote:
On Tuesday 03 December 2002 08:50, Fergus Wilde wrote:
Hi All,
<some snippage> Hi Noodlez,
FYI (and everyone else's), if you have a proper TrueType license, you might want to turn on the bytecode interpreter if you're compiling your own freetype2. You have to edit the ftoption.h file in include/freetype/config and #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER .
Supposedly it gives much better results, but I don't use it as I use the hacked Xft library from http://www.cs.mcgill.ca/~dchest/xfthack/ with Microsoft's TrueType fonts.
The advice at http://www.freetype.org/freetype2/2.1.3-explained.html appears to be that you shouldn't necessarily turn on the bytecode interpreter for this release, because they have their own wonder-weapon: "Short answer: No for most people !! We now highly recommend you to not enable the TrueType bytecode interpreter when installing FreeType. That's because we believe that the FreeType auto-hinter now produces results that out-perform native TrueType hinting when it comes to rendering AA text. However, you might still need it in certain cases, <large snip> ... we invite you to experiment with a fully anti-aliased desktop with FreeType 2.1.3 and no bytecode interpreter. Only if this doesn't suit your needs should you consider downgrading." Presumably this doesn't apply to you if you're using your hacked Xft library, but it might apply to those of us who haven't got into that yet.
Gorgeous... Now if only YaST2 didn't use it's own font and used KDE defaults...
<my silly question and Karol's answer snipped> Thanks for that, now it makes sense! And thanks for putting up your Mplayer rpms, too, they work really nicely. Best Fergus -- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk