[Fontconfig] Strange behaviour with fixed pitch

[Alan Chandler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 02 Feb 2003 8:12 pm, Alan Chandler wrote:
> On Sunday 26 Jan 2003 4:51 pm, Alan Chandler wrote:
> > 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
> > - 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 font that it provides (see
> > http://bugs.kde.org/show_bug.cgi?id=52538 )
>
> Nobody replied to this posting so I STILL don't know if I am at the right
> place.

AND nobody replied to the second posting either:-( - BUT NOW IT THINK I AM AT 
THE RIGHT PLACE.

I have been digging away some more, and in particular in fcmatch.c to find out 
what is happening.  I think the problem is that this routine is trying to 
compare font patterns with a priority order of foundary, character set, 
family (strong), language, family (weak) ...

It does not find the console font as an exact match - what appears to happen 
is that it does find a match with console, but in the fonts pattern there are 
a number of elements.  For the third element font.elt[2]->object = "family" 
but the font.elt[2]->values->value has a string value of "console8x16.pcf" 
(and there are no more values attached to family).  The verdana font is 
eventally seen as a closer match although it only matches on the weak family 
name (I think this has been added to the requesting pattern by fontconfig as 
a result of a Style request from a high level routine for "sans" [and 
translated into sans-serif by fontconfig, and then translated [ie replaced in 
he pattern] to a list of weak matching font names].

The filename in /usr/share/fonts is console8x16.pcf.gz - but if I do a 
xlsfonts - the family name in these fonts is shown as "console".  This 
differs from what fontconfig finds.

I need to find how the "font patterns" are set up from the fonts. Can someone 
explain how this works? [In broad terms only, I can delve into the right bit 
of code one I find it]














- -- 
Alan Chandler
alan at chandlerfamily.org.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+ToM4uFHxcV2FFoIRAoj+AKCqr7UZWs3dLFfcq2O4bmKDDTIJlQCfRF9o
/fewKK5+RQao/u2wbpmGuzU=
=lz+X
-----END PGP SIGNATURE-----