From xemacs-m  Mon Feb 10 16:40:54 1997
Received: from newman (root@newman.aventail.com [38.225.141.10])
	by xemacs.org (8.8.5/8.8.5) with SMTP id QAA15284
	for <xemacs-beta@xemacs.org>; Mon, 10 Feb 1997 16:40:52 -0600 (CST)
Received: from kramer.in.aventail.com.aventail.com (wmperry@kramer [192.168.1.12]) by newman (8.6.12/8.6.9) with SMTP id OAA01958; Mon, 10 Feb 1997 14:39:05 -0800
Date: Mon, 10 Feb 1997 14:39:05 -0800
Message-Id: <199702102239.OAA01958@newman>
From: "William M. Perry" <wmperry@aventail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Martin Buchholz <mrb@Eng.Sun.COM>
cc: xemacs-beta@xemacs.org
Subject: Re: How robust is the mule font code?
In-Reply-To: <199702102204.OAA00033@xemacs.eng.sun.com>
References: <199702101552.HAA32270@newman>
	<199702102204.OAA00033@xemacs.eng.sun.com>
Errors-to: wmperry@aventail.com
Reply-to: wmperry@aventail.com
X-Face: O~Rn;(l][/-o1sALg4A@xpE:9-"'IR[%;,,!m7</SYF`{vYQ(&RI1&EiH[FvT;J}@f!4kfz
 x_!Y#=y{Uuj9GvUi=cPuajQ(Z42R[wE@{G,sn$qGr5g/wnb*"*ktI+,CD}1Z'wxrM2ag-r0p5I6\nA
 [WJopW_J.WY;

Martin Buchholz writes:
>>>>>> "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 "*".

  This is how I do it - you can specify the registry and the encoding.  I
mistyped earlier.

>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?

  Because the specified via Xresources the encoding.  What I need to do is
deal with the 'charset' parameter in HTTP responses and do a mapping from
that to registry/encoding pairs for the font model.  Not sure if I grok
this enough yet.  Oh, to have spare time again.

-Bill P.

