From xemacs-m  Mon Apr 21 14:56:11 1997
Received: from newman (root@newman.aventail.com [199.238.236.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id OAA27383
	for <xemacs-beta@xemacs.org>; Mon, 21 Apr 1997 14:56: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 LAA11141; Mon, 21 Apr 1997 11:23:09 -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> 	<86hgh0kzg3.fsf@kramer.in.aventail.com> <QQcmgr20771.199704211921@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 12:56:09 -0700
In-Reply-To: Kyle Jones's message of Mon, 21 Apr 1997 15:21:28 -0400 (EDT)
Message-ID: <86wwpw6tgm.fsf@kramer.in.aventail.com>
Lines: 44
X-Mailer: Gnus v5.4.45/XEmacs 20.2(beta1)

Kyle Jones <kyle_jones@wonderworks.com> writes:

> William M. Perry writes:
>  >  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.
> 
> You're fighting against the design of the system.  Under MULE font
> specifiers seem to work more like image specifiers.  A font instance has
> to make sense under a particular charset for it to be permitted, just as
> image instance have to make sense on device types and tag sets.  If it
> doesn't make sense, then the spec for a less local domain is tried.
> 
> It would be good if this fit better into the specifier system.  I think
> the charset would have to be in the device tag-set of the specifier, but
> I'd have to think about it more to be sure.

  Exactly - I would expect face-font-name to return
courier-*-*blahblahblah-.  This is why the current fond model sucks.

> But the point is that under the system as it is currently designed what
> you want is a new charset, or perhaps to make the 'ascii character accept
> more registries.  I would prefer that you create a new charset, cuz I
> doubt that I ever want to see those T-bars in a non-Web-page context.  I
> don't know of any apps that create new charsets, so as an Added Bonus you
> get to try it and tell us if it works. :-)

 Ok, so I forgot my crib notes - how do I specify the charset of a region
of text?  Please say I can do it with text properties, otherwise I'll have
to go bite the head off of a live chicken.  Said charset will be _exactly_
like ascii, but accept any registry.

-Bill P.

