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:         Thu, 28 Jun 90 10:17:00 PDT
Reply-To: LaTeX-L Mailing list <LATEX-L%DHDURZ1@unido.bitnet>
From: Don Hosek <DHOSEK@HMCVAX.bitnet>
Subject:      Re: Font mappings
To: Rainer Schoepf <BK4@DHDURZ1.uucp>
Status: R
X-Status: 
X-Keywords:                  
X-UID: 146

>Unless I am being dense, this is what the first parameter
>to \extra@def is for, isn't it? (by the way, having just
>searched the
>files, I can't actually find a definition of the two
>parameters to
>extra@def anywhere...). Frank asked whether there were any
>special
>actions to be taken when a font is used *specifically in
>non-math
>mode*, didn't he?

\extra@def currently has a parameter for actions to be
executed _when_the_font_is_loaded_ and _when_the_font_is_
_used_in_math_mode_, e.g.,
\@extradef{cmtt}{\hyphenchar #1\m@ne}{}

> \typeout{**Using TeX-encoded PostScript fonts
>(Mittelbach/Schoepf method) **}
> \adobeencoding
> \sansfont{lucidasans}%
> \typewriterfont{courier}%
> \romanfont{lucida}%

>the fact that I (the style writer) have to put in that
>\adobeencoding
>seems reasonable to me. the punter will say
>...style[lucida]{...
>anyway.

But suppose the document uses Adobe Helvetica for headings
and Computer Modern for the body text?

-dh