X-VM-v5-Data: ([nil nil nil nil nil nil nil t nil]
	[nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil])
Date:         Wed, 27 Jun 90 12:12:16 bst
Reply-To: LaTeX-L Mailing list <LATEX-L%DHDURZ1@unido.bitnet>
From: Sebastian Rahtz <spqr@ECS.SOTON.AC.UK>
Subject:      Re: font selection
To: Rainer Schoepf <BK4@DHDURZ1.uucp>
Status: R
X-Status: 
X-Keywords:                  
X-UID: 141

PZF5HZ@EARN.RUIPC1E writes:

 > I wonder whether we should add a third arguement which would
 > hold <actions to be performed whenever a font of this family is
 > used in ordinary text>.
 >
 > The reason why I'm asking this is that this will allow to
 > rearrange charmappings, for example, if postscript and other
 > fonts are used together. On the other hand (and that's the reason
 > why it is not included so far) it will slow down the processing.
I take the point; but it seems quite a high price to pay for a
marginal convenience. I would assume that virtual fonts, or other
mechanisms, would do the same job for mapping.

 > 1) Do you see applications where it is necessary to perform
 >    actions whenever a family changes?
*if* we didn't have virtual fonts, yes. Mapping *is* important, and a
huge problem when you use `foreign' fonts. but most changes one might
want to make (printing things in grey? changing hyphenation?) might as
well be done in the normal way. Thus I have a command \adobeencoding
which switches to Adobe mapping. You want me to be able to tie this to
family `times', but why not just say:

 \family{times}\adobeencoding

or, more likely,
 \def\Times{\family{times}\adobeencoding}
 \Times

or am I missing something?

Sebastian