🚀 go-pugleaf

In article <379@h-three.UUCP> jimi@h-three.UUCP (jimi) writes:
>In article <1221@tmpmbx.UUCP>, csch@tmpmbx.UUCP (Clemens Schrimpe) writes:
>> jos@idca.tds.PHILIPS.nl (Jos Vos) writes:
>> <> Can anybody give me some suggestions about the two-letter fontnames for
>> <> [di]troff that I should assign to the 35 built-in fonts of the Apple
>> <> LaserWriter IINTX? Of course I can define some (sometimes even reasonable)
>> <> names, but I want to use standards as much as possible.

Another convention to consider is that of Adobe Systems, creators of TranScript.
I append a table taken from a man page I wrote which I believe has been
incorporated in modified form into TranScript.  The naming convention is NOT
mine; I bridled against it at first, but now find it sensible; the regular font
is 2 lower-case letters; the bold version capitalizes the first, italic
capitalizes the second, and bold-italic cpaitalizes both.  The exceptions
are the Times fonts and Courier, as an earlier usage is so well entrenched.
I include some notes about ditroff font bugs bugs and work-arounds.

PostScript Name		C*	PostScript Name			C*
---------------		--	---------------			--
AvantGarde-Book		ag	Helvetica-Narrow-Oblique	hN
AvantGarde-BookOblique	aG	Helvetica-Narrow-Bold		Hn
AvantGarde-Demi		Ag	Helvetica-Narrow-BoldOblique	HN
AvantGarde-DemiOblique	AG	NewCenturySchlbk-Roman		nc
Bookman-Light		bo	NewCenturySchlbk-Italic		nC
Bookman-Italic		bO	NewCenturySchlbk-Bold		Nc
Bookman-Demi		Bo	NewCenturySchlbk-BoldItalic	NC
Bookman-DemiItalic	BO	Palatino-Roman			pa
Courier			C	Palatino-Italic			pA
Courier-Oblique		CO	Palatino-Bold			Pa
Courier-Bold		CB	Palatino-BoldItalic		PA
Courier-BoldOblique	CD	Symbol				S
Helvetica		he	Times-Roman			R
Helvetica-Oblique	hE	Times-Italic			I
Helvetica-Bold		He	Times-Bold			B
Helvetica-BoldOblique	HE	Times-BoldItalic		BI
Helvetica-Narrow	nh	ZapfChancery-MediumItalic	ZC
				ZapfDingbats			ZD
-------------------
* ditroff font code

IMPORTANT NOTES ABOUT DITROFF USAGE (BUG WORK-AROUNDS)
AT&T and Berkeley-enhanced device-independent troff(1),
or ditroff(1L), as accessed in TrnaScript by the psroff(1L)
command,  exhibit the following problems regarding font changes:

1) There are 10 premounted fonts, corresponding to font codes
R I B BI H He C CB S in the above chart, and including a special
extension to the S font known as SS (this extension set is never
accessed directly as an independent font and therefore does not appear in the
table).  These fonts are mounted in positions 1 through 10; fonts other
than these can be EXPLICITLY MOUNTED in any numerical position with the
ditroff(1L) .fp command (avoid using positions 9 and 10 which are
occupied by the S and SS font sets).
The amount of memory available for a given font position is fixed
(during the initialization of ditroff(1L)) to the size of the font
first mounted there; if a later attempt is made to mount a larger font in this
position, ditroff(1L) prints an error message about the requested font
being too large for the position.  The positions initially occupied by the
Courier fonts (positions 7 and 8) seem particularly prone to this problem,
which can be minimized by explicitly mounting a font prior to its use, into
a position occupied by a large font.  For example, the Zapf Chancery font
can be mounted in position 6 with the command: .fp 6 ZC.  The font
position MUST be between 1 and 10.

2) If an unmounted font is requested via a ditroff(1L) \f
command, it is automatically mounted into a special font position numbered 0.
(I will refer to this process as IMPLICITLY MOUNTING a font).
The font size problem can also arise, in which case explicitly mounting the
needed font (into position 6, for example) can again solve the problem.

3) There is a bug in ditroff(1L) such that use of more than one
implicitly mounted font within the same output line causes the incorrect
font metrics to be used (causing incorrect character spacing).  The solution
to this problem is to explicitly mount each font to be used prior to using
the \f command.

4) Beware of some earlier versions of psdit(1L), in which characters
appearing immediately prior to the implicit mounting of a font may be
printed over one another.

5) There is an (as yet poorly characterized) bug in Berkeley ditroff(1L)
which causes incorrect fonts to be employed when explicitly mounted fonts
are mounted implicitly.  For example, mounting the Times Roman font in
position 2 can lead to this problem.  The problem appears to arise when
the \fP command is subsequently used (the system does not return to
the correct previous font). However, maneuvers such as mounting hn onto
position 2 (normally employed by Times Italic),  and then later
remounting I onto position 2, seem to work.