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:37:53 bst
Reply-To: LaTeX-L Mailing list <LATEX-L%DHDURZ1@unido.bitnet>
From: spqr@ECS.SOTON.AC.UK
Subject:      Re: Font mappings
To: Rainer Schoepf <BK4@DHDURZ1.uucp>
Status: R
X-Status: 
X-Keywords:                  
X-UID: 145

Don Hosek writes:

 > would like to make it a fairly trivial exercise for the author to
 > switch between, say, PS versions of Times, Helvetica, Century
 > Schoolbook, and Optima, Xerox Merganthaler versions of those
 > fonts, and Compugraphic versions. Each of these may require a bit
 > of extra setup which is different. Since this setup is logically
 > tied to the family, I think that the other code should be tied up
 > to the family as well.
There's an age old argument here about how much gets packaged up for
the user in style files, and how elegant those style files are. My
style option to typeset in Lucida lools like this:
 \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.

 > Case two: Cyrillic and Greek alphabets. These need extra setup no
 > matter how you try to deal with them. The extradefs for Greek, for
 > example, might include definitions to select the proper
 > hyphenations and set up the active characters necessary for Greek.
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?

Sebastian

(PS yes I am receiving this again. our mail software finally talks to
earn-relay again)