On 24 Jun 2003 23:31:07 +0200 Soeren Sandmann <sandmann@daimi.au.dk> wrote: <snip> > > The variant that I use is > > <match target="font"> > <test qual="any" name="size" compare="less"> > <double>14</double> > </test> > <test qual="any" name="size" compare="more"> > <double>8</double> > </test> > <edit name="antialias" mode="assign"> > <bool>false</bool> > </edit> > </match> > > Ie. antialias, but only when the size is below 8 or above > 14. This is an approximation on what windows does. Windows > uses extra information in the fonts about when to > antialias that is unfortunately not available though > FreeType. > > There are various other possibilities that look good, > including"antialias, but turn off hinting". As you found > out, having *both* bytecode interpreter and antialiasing > for normal screen-sized fonts is just about the worst > thing you can do to your > fonts. Thank-you Soeren. This has been an extremely useful thread for me, and I will experiment further. I am especially interested to learn about the evils of combining the bytecode interpreter with antialiasing. I will do some recompiling and experimentation. Regards, Geoff
