=2D----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 assu= me > > - 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=3D52538 ) > > 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=20 THE RIGHT PLACE. I have been digging away some more, and in particular in fcmatch.c to find = out=20 what is happening. I think the problem is that this routine is trying to=20 compare font patterns with a priority order of foundary, character set,=20 family (strong), language, family (weak) ... It does not find the console font as an exact match - what appears to happe= n=20 is that it does find a match with console, but in the fonts pattern there a= re=20 a number of elements. For the third element font.elt[2]->object =3D "famil= y"=20 but the font.elt[2]->values->value has a string value of "console8x16.pcf"= =20 (and there are no more values attached to family). The verdana font is=20 eventally seen as a closer match although it only matches on the weak famil= y=20 name (I think this has been added to the requesting pattern by fontconfig a= s=20 a result of a Style request from a high level routine for "sans" [and=20 translated into sans-serif by fontconfig, and then translated [ie replaced = in=20 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=20 xlsfonts - the family name in these fonts is shown as "console". This=20 differs from what fontconfig finds. I need to find how the "font patterns" are set up from the fonts. Can someo= ne=20 explain how this works? [In broad terms only, I can delve into the right bi= t=20 of code one I find it] =2D --=20 Alan Chandler alan@xxxxxxxxxxxxxxxxxxxxx =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+ToM4uFHxcV2FFoIRAoj+AKCqr7UZWs3dLFfcq2O4bmKDDTIJlQCfRF9o /fewKK5+RQao/u2wbpmGuzU=3D =3Dlz+X =2D----END PGP SIGNATURE-----
