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 10:40:35 CET
Reply-To: LaTeX-L Mailing list <LATEX-L%DHDURZ1@unido.bitnet>
From: PZF5HZ@RUIPC1E.bitnet
To: Rainer Schoepf <BK4@DHDURZ1.uucp>
Status: R
X-Status: 
X-Keywords:                  
X-UID: 139

I have a small problem concerning the new font selection
scheme.

At the moment for every family like cmr or cmss we have an
\extra@def macro defining actions which should be performed
when a new font of this family is used.

the syntax is:

\extra@def{cmtt}{<action performed when a new font is loaded>}
                {<action performed whenever the font is used
                  in math mode>}

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.

Another possibility would be to wait for virtual fonts. But
even then there would be some arguments in favor of this change.

Since the fontselection scheme is currently been released and this
is an interface change in the fontdef file I would be glad if you
can give your opinion about this fast.

Questions I would like to get answers to:

1) Do you see applications where it is necessary to perform
   actions whenever a family changes?

2) Do you think mapping is a legitimate action?
   (The Kinch AP-TeX fonts are already in TeX mapping)

3) Or should we say that the virtual font concept makes mapping
   unnecessary?

It would be fine if most of you find the time to answer.

Frank Mittelbach