From xemacs-m  Mon Feb 10 16:04:38 1997
Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5])
	by xemacs.org (8.8.5/8.8.5) with SMTP id QAA14349
	for <xemacs-beta@xemacs.org>; Mon, 10 Feb 1997 16:04:37 -0600 (CST)
Received: from Eng.Sun.COM ([129.146.1.25]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id OAA06395; Mon, 10 Feb 1997 14:04:05 -0800
Received: from kindra.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3)
	id OAA09990; Mon, 10 Feb 1997 14:04:03 -0800
Received: from xemacs.eng.sun.com by kindra.eng.sun.com (SMI-8.6/SMI-SVR4)
	id OAA23120; Mon, 10 Feb 1997 14:04:02 -0800
Received: by xemacs.eng.sun.com (SMI-8.6/SMI-SVR4)
	id OAA00033; Mon, 10 Feb 1997 14:04:01 -0800
Date: Mon, 10 Feb 1997 14:04:01 -0800
Message-Id: <199702102204.OAA00033@xemacs.eng.sun.com>
From: Martin Buchholz <mrb@Eng.Sun.COM>
To: wmperry@aventail.com
Cc: xemacs-beta@xemacs.org
Subject: How robust is the mule font code?
In-Reply-To: <199702101552.HAA32270@newman>
References: <199702101552.HAA32270@newman>
Reply-To: Martin Buchholz <mrb@Eng.Sun.COM>
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII

>>>>> "Bill" == William M Perry <wmperry@aventail.com> writes:

Bill> Would I break anything if I explicitly set the encoding of fonts
Bill> to iso8859-1 instead of '*' from within the font package?  It is

Yes, you would break things. iso8859-1 is evil.  Each charset has a
corresponding (charset-registry).  The idea is that a user ought to
specify fonts using "*-*" in the registry-encoding fields, and XEmacs
uses only fonts matching the charset-registry for a particular charset
when displaying characters in that charset.  It's really rather nice
that in a CDE environment, one can do

(set-face-font 'default "-dt-interface user-medium-r-normal-s*-*-*-*-*-*-*-*-*")

and have a good chance that that will work for *ALL* locales supported
by CDE.

By the way, it is also a good idea to use font specification patterns
that are WELL-FORMED, i.e. that have all 14 (!) hyphens defined in the
XLFD.  In particular, use "*-*" for the registry-encoding fields, not
just "*".

Bill> picking up hp-roman8 encodings on some systems, which is just
Bill> wrong.  I don't want to screw up the multilingual stuff in W3
Bill> though.

Why would users get this hp-roman8 font in a W3 buffer, but not in an
ordinary buffer?

I made the highly controversial decision to use a different
charset-registry for the 'ascii charset when setting the language
environment to Chinese/Japanese/Korean.

(charset-registry 'ascii)
"JISX0201"

This means that iso8859-1 fonts are only used for the upper half of
iso8859-1, not for plain ascii.

Martin

