[Fonts] No bitmapped fonts in Qt 3.1.1

2003-02-08 Thread Nathaniel Gray
I've got the same problem.  I don't know if it's a Qt problem or an X 
problem though.

XFree86 4.2.99.4, Qt 3.1.1, KDE 3.1

Cheers,
-n8
-- 
>>>-- Nathaniel Gray -- Caltech Computer Science -->
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->

___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts



[Fonts] No bitmapped fonts in Qt 3.1.1

2003-01-29 Thread Martin van Es
Hi,

I've been having on and off (more off lately) experiences with AA and
BitMapped fonts under Qt 3.x. since I started compiling Xfree86 from CVS
(4.2.99).
At first AA fonts were disabled, then I had AA and BM'd and now only
AA'd fonts.

Don't get me wrong: I LOVE AA'd fonts, it's just that I'd like to use
some of the BM'd fonts for my KDE interface as well (I like 'Clean' a
lot!).

All BM'd fonts show up in my fontlist, but they display as some default
AA'd font (I suspect Helvetica) with too much whitespace between the
characters. I'm a bit confused who's responsible for what when it comes
to fonts. There is xft, xft2, fontconfig xrender etc.

I compiled Qt 3.1.1 from source (with Xft support, more than once).

What am I missing/doing wrong?
I'm having troubles 'reading' the new font.config format, might there be
some aliases that are ruining it for me? Old configs/stale installations
seem impossible, since I allways compile X to a fresh X11R6/ directory,
unless I am suffering from old configs somewhere in /etc?

The symptoms are the same in qtconfig and The KDE font controlpanel
module, so I suspect the problem to be at Qt/Xfree-level.

Oh erm one last important remark: bitmapped fonts _do_ work in xterm
(etc).
It's really that Qt vs. XF-4.2.99 messes up for some reason.


Regards,
Martin

___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts