Hi, This is the official reply I got from Trolltech when I told them about the problem while XFree was still in beta (2.4.99):
----------- > [Snip: My question about AA'd and BM'd fonts being mangled] It seems that you have been affected by the ever changing Xft library. XFree86 4.2.1 still ships with Xft1, and the last Qt 3.0.x release only supports Xft1. Xft2 has been "released" separately from the XFree86 tree, and so we needed to add support for this in Qt 3.1.x. The current 3.1.x releases support Xft2, while maintaining Xft1 support. Rather long history lesson, what does it mean? I haven't seen any such problems here with 3.1.x and Xft2 from the fonconfig 2.1 "release". If you have intermittent problems that popup after upgrading XFree86, then they must be specific to Xft in CVS, and nothing we can work around in Qt. > All XFree applications as well as GTK applications that I run > understand, see and render bitmapped fonts without a problem > (xterm/Phoenix (Mozilla) etc). Qt applications do show the bitmapped > fonts in the fontlist, but render them as some AA'd font (Lucida > alike) with wrong (too wide) spacing. This is mostly due to a misunderstanding of Xft works. Originally, we were told it was similar to the standard XLFD interface. We quickly found out that it was not, and much of our logic was broken due to some changes in Xft. We are addressing this issue, and will have this working in Qt 3.2.0. We have considered fixing this for 3.1.x, but unfortunately the changes are too intrusive to do. --------------- Regards, Martin van Es _______________________________________________ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
