It looks like the solution for this problem is going to involve
application-level fixes.
----- Forwarded message from Juliusz Chroboczek <[EMAIL PROTECTED]> -----
From: Juliusz Chroboczek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Debian and bug reports
Date: Sun, 19 Nov 2000 23:22:24 +0100 (CET)
Delivered-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
X-Authentication-Warning: cedre.ens.fr: jch set sender to [EMAIL PROTECTED] using -f
In-reply-to: <[EMAIL PROTECTED]> ([EMAIL PROTECTED])
BR> http://bugs.debian.org/76280
It looks like some font names are underspecified. If you request a
font such as
-misc-fixed-medium-r-normal--12-*-*-*-c-*-*
then the first matching font will be selected; which font is the first
depends on many factors, like the exact details of the hashing
algorithm used in the server.
In order to avoid that, you should more fully specify the font, saying
something like:
-misc-fixed-medium-r-normal--12-*-*-*-c-iso8859-1
This change should be made either in the users resource database
(xrdb, .Xdefaults, etc.), or in the application defaults files
(XTerm.ad, etc.), depending on the exact setup that you're using.
(What changed in 4.0? We're now including many more international
fonts, so the likelyhood of a wrong font being selected is much
higher.)
Regards,
Juliusz
----- End forwarded message -----
--
G. Branden Robinson | Q: How does a Unix guru have sex?
Debian GNU/Linux | A: unzip;strip;touch;finger;mount;fsck;
[EMAIL PROTECTED] | more;yes;fsck;fsck;fsck;umount;sleep
http://deadbeast.net/~branden/ |
PGP signature
