From xemacs-m  Mon Apr 21 13:23:12 1997
Received: from newman (root@newman.aventail.com [199.238.236.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id NAA26132
	for <xemacs-beta@xemacs.org>; Mon, 21 Apr 1997 13:23:11 -0500 (CDT)
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 JAA11093; Mon, 21 Apr 1997 09:50:08 -0700
To: Kyle Jones <kyle_jones@wonderworks.com>
Cc: xemacs-beta@xemacs.org
Subject: Re: Impossible to use 'terminal' font in XEmacs/mule
References: <86pvvov2q4.fsf@kramer.in.aventail.com> 	<9704211513.AA24209@fornet.gvc.dec.com> 	<86ohb8v0o7.fsf@kramer.in.aventail.com> 	<QQcmge18104.199704211606@crystal.WonderWorks.COM> 	<86d8ro8iar.fsf@kramer.in.aventail.com> 	<9704211639.AA24314@fornet.gvc.dec.com> 	<QQcmgl19447.199704211745@crystal.WonderWorks.COM> 	<86iv1gl0p8.fsf@kramer.in.aventail.com> <QQcmgm19814.199704211811@crystal.WonderWorks.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;
From: wmperry@aventail.com (William M. Perry)
Date: 21 Apr 1997 11:23:08 -0700
In-Reply-To: Kyle Jones's message of Mon, 21 Apr 1997 14:11:36 -0400 (EDT)
Message-ID: <86hgh0kzg3.fsf@kramer.in.aventail.com>
Lines: 30
X-Mailer: Gnus v5.4.45/XEmacs 20.2(beta1)

Kyle Jones <kyle_jones@wonderworks.com> writes:

> William M. Perry writes:
>  > this just seems inherently silly.  This basically means you
>  > cannot display fun little characters outside of ISO8859-1 in a
>  > buffer without defining your own frigging character set!
> 
> Yes, I think you are correct.  But I don't think it's silly.  How else
> can MULE determine whether a charset set can be displayed with a given
> font?  If I want to display ASCII, I certainly don't want the code to
> pick any of the versions of the terminal fonts that display half the
> characters as T-bars.  I think the use of the registry information is
> exactly right.

 I think that if I explicitly set a font for a face, it should be honored
for an ascii environment.  _Especially_ if I specify the ENCODING.  End of
story.

This is sure as hell wrong:

(set-face-font 'default
	       "-bitstream-terminal-medium-*-*-*-*-*-*-*-*-*-dec-dectech"
	       (current-buffer))
"-bitstream-terminal-medium-*-*-*-*-*-*-*-*-*-dec-dectech"
(face-font-name 'default (selected-window))
"-bitstream-terminal-medium-*-*-*-*-*-*-*-*-*-dec-dectech"

And the actual font being used is the global default font.

-Bill P.

