On Sun, 2006-02-12 at 23:17 +0100, Jan Willem Stumpel wrote: > It seems the problem can be narrowed down to xprint's inability to > recognise the *generic* font family names (serif, sans-serif, monospace) > used by fontconfig (but xprint does not use fontconfig). It only > recognises specific names. >
Excellent detective work, Jan. Sounds like it might be an idea to add fontconfig support, though I don't know right at this moment how feasible that would be. Thanks for the good efforts. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
