On Wed, 14 Mar 2001, Vadim Plessky wrote:
> On Tuesday 13 March 2001 11:37, you wrote:
> | Ok, it seems I have it generally working now. I have attached a patch to
> | kdelibs that lets KDE Applications use the font substitutions defined in
> | XftConfig and lets users select fixed width fonts.
> | It seems that both Qt and XFree86 are far from complete with regard to
> | Antialiasing support, but this will help work around the biggest
> | problems.
>
> What version of QT do you use?
> Recommended version is QT 2.3 (not 2.2.4).
>
I am using qt 2.3 and upgrade cooker daily from ftp.sunet.se.
The problem with this is that it still behaves differently for Xft fonts
than for regular fonts served by xfs.
In particular, the QFontDatabase class seems not to contain sufficient
information about font properties like foundry and spacing.
KDE on the other hand relies on this information and it needs all fonts to
be in the database, but when you replace a font through XftConfig, e.g.
substitute Helvetica by Verdana, it does not find it.
> As about AA in XFree86 - ATI (mach64) support was added to XF *after* XF
> 4.0.2 release. I don't know which branch of XF RPM in Cooker is based on, but
> XF 4.0.99 (pre-release of 4.1) most likely has the best AA support for
> different cards/drivers.
Hmm, I just looked at the libXft in both cookers XFree86 and XFree 4.0.99 from
CVS. Unlike I thought, it should actually be possible to use regular bitmap
fonts also with Xft, which would solve all problems here.
Unfortunately the current version does not return those fontnames in
XftListFonts() when XFT_CORE = true is not specified. This means that
Qt never finds out they actually exist.
>
> I have also heard from Vladimir Dergachev that Xv support for ATI cards can
> be added to XF 4.1 (have no confirmation about it, though...)
> AFAIK Cooker still has XF 4.0.2.
It's built from XFree86-4.0.2-branch-20010308.tar.bz2, so I guess that's
the CVS version of the upcoming 4.0.3.
Arnd <><
