Xref: utzoo comp.text:2598 comp.lang.postscript:1043
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!gatech!ncsuvx!mcnc!rti!h-three!jimi
From: jimi@h-three.UUCP (jimi)
Newsgroups: comp.text,comp.lang.postscript
Subject: Re: Troff font names for PostScript fonts
Summary: just kidding about ANSI/ISO
Keywords: DWB troff ditroff PostScript LWIINTX
Message-ID: <380@h-three.UUCP>
Date: 13 Oct 88 05:27:33 GMT
References: <570@ssp15.idca.tds.philips.nl> <1221@tmpmbx.UUCP> <379@h-three.UUCP>
Organization: h-three Systems, Research Triangle Park,  NC
Lines: 41

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.
> > 
> > [deleted]
> 
> It's hard to argue, except "religiously," in favor of one [set of
> names] or [another]; this is a good example of a standard that's
> really needed. Any standards groups want to make this an ANSI/ISO
> standard?

I really should have put a *8^) after the preceding paragraph in my
previous posting. It's hard to imagine an ANSI/ISO standard that
specifies troff font names, especially since what a font name means
on one device might name an different font on another device (e.g.,
does HO stand for Helvetica Outline or Helvetica Oblique? On a
phototypesetter I use, Helvetica Oblique is called Triumvarate
Italic.).  Since it's so easy in troff to map one font name to another
name or number, font names need not be an obstacle in the exchange
of revisable form troff documents.

> > [table of font names deleted]

One standard that might make sense is for the set of special character
names that might occur in a troff rf document. It's inconvenient to
use PostScript's native method of character encoding in troff documents, 
and it's inconvenient to map one set of character names to another. The
characters I'm thinking about include the fairly standardized set of
names for typographical symbols, the national characters, math symbols,
etc. Such a standard needn't apply only to PostScript output devices.

This discussion is moving away from PostScript. Perhaps it should
continue, if at all, in comp.text.

-- 
Jim Ingram	          uunet!h-three!jimi | jimi%h-three@uunet.uu.net
h-three Systems Corporation   P.O. Box 12557 RTP NC 27709   919 549 8334