On Fri, 16 Mar 2001, Ed Wilts wrote:
> On Friday 16 March 2001 04:27, Claudio (sekko) wrote:
>
> > My question is: in incoming 8.0 will antialiasing work? Anyway it could be
> > really usefull to clean up this option if possible, or (at least) to leave
> > it off by default! Thanks,
>
> Antialiasing works now, so why should it not work with 8.0?
It does not yet work by default. You still have to manually edit XftConfig
to reflect your font directories and/or get Keiths truetype.tar.gz.
Depending on the installed fonts, you also have to change the font settings
In the KDE control center and konsole is still broken.
I posted a workaround for this earlier, but the real problem is still on
a lower level in Qt or in Xft.
> I will assume that you've read and followed one of the many posts on how to
> actually make it work...
Most of the future users of 8.0 have not read them. I think it is vital
to have it working without any additional configuration if it should be the
default.
> LinuxPlanet just did an anrticle on anti-aliasing as well, and it's fairly
> straightforward.
The stuff covered by the article is mostly irrelevant because the problems
described there are already solved in cooker.
Although it can be made to work for most people, font antialiasing is still
an alpha feature from the unsupported tree of XFree86.
It breaks heavily if you don't install any Truetype/Type1 fonts or have
the wrong graphics card, like dual head Matrox, iirc.
You will also get massive slowdown when you have many fonts installed.
On my 800 Mhz Athlon, Qt applications need up to two seconds more for startup
with AA than normal. I have about 40 fonts installed, most of them
come in four different variations (bold, italic, ...).
It is also still not possible to run mc or any other application using
ascii-pseudographics in konsole.
Each of this is enough justification _not_ to enable it by default. Users
will complain.
Arnd <><
