[Fontconfig] Strange behaviour with fixed pitch

Alan Chandler fontconfig@fontconfig.org
Sun, 26 Jan 2003 16:51:56 +0000


=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am not sure that I have found the right place to ask this question.

A few weeks ago, I installed fontconfig (Debian Unstable), with (I assume -=
=20
and thats why I am not sure I am at the right place) libxft2.

Since then, I have had a strange problem in kde (konsole) with the console=
=20
font that it provides (see http://bugs.kde.org/show_bug.cgi?id=3D52538 )

I have been trying to debug the problem over the last couple of weeks and h=
ave=20
narrowed it down to the fact that using QT - if I toggle the FixedPitch=20
property of the font that a piece of text is displayed in the text display=
=20
displays normally when the Fixed Pitch attribute is off and seems to have a=
=20
double width spacing when the Fixed Pitch attribute is on.

With a small application doing just that - I have been running a debugger i=
nto=20
the qt code to find why it changes the character spacing.  Its difficult to=
=20
be sure but I am almost convinced that when it calls the xft library to=20
render the text it does not know that it will be rendered at this double=20
width.  Clipping Rectange sizes etc seem to be being calculated on the basi=
s=20
of the correct font metrics.  Trouble is, I haven't manage to discover how=
=20
the Fixed Pitch attribute is propagated down to the xft library - so I can'=
t=20
quite explain everything.

If my suposition is correct, then it is libxft2 that has the fault. Reading=
=20
the info at www.fontconfig.org the suggestion is that its using a different=
=20
version of the library that xfree.

So - I am reporting it here.

PS - trying to join mailing list but my membership hasn't come through yet =
(is=20
it moderated?) so maybe a cc to me on a reply would help - thanks.=20
   =20
=2D --=20
Alan Chandler
alan@chandlerfamily.org.uk
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+NBIwuFHxcV2FFoIRAnCoAJ9g42MG5tjsRA4d1tkHTJ429n80JACgigaX
MnCYHKDXcKLpdlK/iNpxaCg=3D
=3DEsww
=2D----END PGP SIGNATURE-----