Received: by nummer-3.proteosys id <01C19442.D61A54D4@nummer-3.proteosys>; Thu, 3 Jan 2002 11:38:52 +0100 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]) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19442.D61A54D4" x-to: LATEX-L%DHDURZ1.BITNET@CUNYVM.CUNY.EDU X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: naming convention for the Pandora fonts Date: Thu, 25 Oct 1990 17:29:40 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "bbeeton" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 256 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19442.D61A54D4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable regarding variations in the names of pandora fonts, i can explain the "short forms" in (2) (though not the "bx", which neenie says she never made). there are some systems that restrict(ed) file names to 6 characters. one such was the dec-10 (on which tex was first implemented). another machine with a limited name length still in use is apparently the cray (i heard this from bart childs). to accommodate such a limitation, the algorithm (first 3 + last 3) was agreed on; so fonts should be named so that when the middle is dropped out the names are still unique. thus pnsx10 comes from pnssbx10 (however misguided the bx), and pnsi10 comes from pnssi10. and (2) is equivalent to (3) modulo the change from b to bx. there is some chance that changes in files that call for fonts might have to be made for such systems, unless the compaction algorithm is actually implemented as a system-dependent modification to tex. (i don't know whether that would render an implementation unable to pass the trip test or not, but that probably shouldn't affect any naming decisions here.) -- bb ------- ------_=_NextPart_001_01C19442.D61A54D4 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: naming convention for the Pandora fonts

regarding variations in the names of pandora fonts, i = can explain the
"short forms" in (2) (though not the = "bx", which neenie says she never
made).
there are some systems that restrict(ed) file names = to 6 characters.
one such was the dec-10 (on which tex was first = implemented).
another machine with a limited name length still in = use is apparently
the cray (i heard this from bart childs).  to = accommodate such a
limitation, the algorithm (first 3 + last 3) was = agreed on; so fonts
should be named so that when the middle is dropped = out the names are
still unique.
thus pnsx10 comes from pnssbx10 (however misguided = the bx), and
pnsi10 comes from pnssi10.  and (2) is = equivalent to (3) modulo the
change from b to bx.
there is some chance that changes in files that call = for fonts might
have to be made for such systems, unless the = compaction algorithm is
actually implemented as a system-dependent = modification to tex.  (i
don't know whether that would render an = implementation unable to pass
the trip test or not, but that probably shouldn't = affect any naming
decisions here.)
        =         =         =         =         =         -- bb
-------

------_=_NextPart_001_01C19442.D61A54D4--