[Fontconfig] confused about <alias> <prefer>

[Alan Chandler]

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

On Wednesday 26 Feb 2003 9:48 pm, Keith Packard wrote:

> The generic names are often provided by the application and end up (by
> default) with strong binding.  Perhaps the problem here is an application
> using the "generic" name 'fixed' which in fact matches actual fonts.  The
> proper generic name is 'monospace', which won't match any fonts.
>
=2E..

> I guess I'm still confused over what the actual problem is here.

Now you've explained it in that way - I see the problem can be seen from a=
=20
different direction.  KDEs konsole has a mode in which it wants to use a=20
"default" font as the font that is used.  It actually translates that as a=
=20
"fixed" family request through qt and then fontconfig (strongly bound) and=
=20
"monospace (weakly bound) (using QFont::Typewriter style hint).=20

Because on Debian there is a strange font in the xfonts-base package (see m=
y=20
post earlier about the "Additional Style" field in an XLFD) which has famil=
y=20
name "fixed" it is found by the fontconfig matching mechanism in preference=
=20
to any other.  I can't remove that xfonts-base package because then the=20
xserver complains it can't find the "fixed" font and won't start.=20

A problem with no obvious way out - except by trying to get "fixed"=20
overwridden when fontconfig does its matching.

I can get round the problem using the match pattern stuff in local.conf but=
 I=20
am also interested in the "correct" way of solving this issue. =20


=2D --=20
Alan Chandler
alan@chandlerfamily.org.uk
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+XUSXuFHxcV2FFoIRAgukAJ0UaTX1wOpnw2q4rFa7BGf1i3669wCePHB0
phTnqZ0H4y/br7Tqesfaqtc=3D
=3DBBd0
=2D----END PGP SIGNATURE-----