Gnome 2.18 bytecode renderer enabled, but still ugly aliased fonts

2007-11-06 Thread Soner Tari 
I am running Gnome 2.18 on 4.2-release. Thanks again to all those who
worked on this port. It's quite stable and functional.

I want to use Tahoma as my ui font, and have disabled anti-aliasing
using gnome-font-properties. Also, I have undef'd
TT_CONFIG_OPTION_NO_INTERPRETER (thus enabled bytecode renderer) by
removing the relevant patch from freetype-1.3.1 patches directory, which
disables it. Make installed freetype.

But Tahoma (and other similar fonts) still looks ugly. Do I need to do
anything else? Could somebody help?

Re: Gnome 2.18 bytecode renderer enabled, but still ugly aliased fonts

2007-11-06 Thread Jonathan Schleifer 
-BEGIN PGP SIGNED MESSAGE-

Hash: RIPEMD160



Soner Tari [EMAIL PROTECTED] wrote:



 But Tahoma (and other similar fonts) still looks ugly. Do I need to do

 anything else? Could somebody help?



Disable the autohinter.



- -- 

Jonathan

-BEGIN PGP SIGNATURE-



iQGVAwUBRzC8sUab4FbSWhEgAQOx7wv/YEkNMsvtge4GzfwDyR9inQIPUtpQKIp/

qcg6zyqvTLGF/kRgs8vodcjwhxrh5OpHz/o0c1cIB2wFdd2xlRAqfn95T0REISlZ

ckii9EeAR1aH+kTyLtao7lAj77MWk7RUzruPoZlYMrmyO1/ZTg9VcZmlBsOgEMaa

VQ0n5E2jzqEZrcZBnmHUAYfgZcqWXf9UsmRsHfXcoeBBblmp6h/QI6ehNyTJqlDk

LyZUhkL9Y8u1OfRlQXJj2OEiypGli2ISP+rQKHiqC6SlWhk9DK3iia4nOv+ob05n

i/ybUv1JcYoFKyrinddgoHPXZG+5ee88Y4XZyJXvzXRHTGRss7XwKRdIq7h83npW

jxytBthyOb3fQkkWNvB38+AR7FUYqdpPz4YMWvsYUaH9nNS2V/7VkkK30LeW7/I2

h86rctVMZfKrNNt0SzheoCQT8HiLxlp5ej2T31tM2g+S2ANB8aOQ8pXWWJCCQpsm

si0NEp9ys46HH/E7Hz6jtX7p5VXU5V2D

=8xU0

-END PGP SIGNATURE-

Re: Gnome 2.18 bytecode renderer enabled, but still ugly aliased fonts

2007-11-06 Thread Soner Tari 
On Tue, 2007-11-06 at 20:12 +0100, Jonathan Schleifer wrote:
  But Tahoma (and other similar fonts) still looks ugly. Do I need to
 do
  anything else? Could somebody help?
 
 Disable the autohinter.

Thanks Jonathan, that was it. (For the record, I've disabled autohinter
in its conf file under /etc/fonts/conf.d)