Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!sdd.hp.com!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!ox-prg!culhua!Damian.Cugley From: Damian.Cugley@prg.ox.ac.uk (Damian Cugley) Newsgroups: comp.text.tex Subject: Re: RFC -- a TeX font naming system Message-ID: Date: 22 Apr 91 16:43:43 GMT References: <1991Apr20.214907.13178@sq.sq.com> Sender: news@prg.ox.ac.uk Organization: Computing Laboratory, Oxford University, UK Lines: 67 In-reply-to: lee@sq.sq.com's message of 20 Apr 91 21:49:07 GMT From: Liam R. E. Quin Message-Id: <1991Apr20.214907.13178@sq.sq.com> > Note that it is useful to separate weight (bold, medium) from face (roman, > oblique, slanted, italic), so that using "cbo" for Courier-Bold-Oblique is > probably bad. I am combining the "face" info into one word for several reasons: firstly, TeX has no useful way to treat weight, width, slant etc. separately; secondly, it's shorter; thirdly, it allows the old fonts -- cmr12 etc. -- to remain unchanged. I prefer Adobe-NewCenturySchoolbook-r (PostScript fonts are linearly scaled, so no is needed) to the XLFD name -Adobe-New Century Schoolbook-Medium-I-Normal--24-240-75-75-P-136-ISO8859-1 if only because it is shorter -- and IMO more comprehensible. For three-part names, the "cut" part is just the "bold-oblique" part of the name. The extra "c" at the front is so that Courier doesn't get called "Adobe-Courier-", with nothing after the final "-". On second thoughts, a better approach would be to drop that and use "r" (= roman or regular) for the regular face: Adobe-Courier-r Adobe-Courier-b Adobe-Courier-o Adobe-Courier-bo also "u" might be used to prefix a Univeseque numeric style description (so s don't start with digits: Linotype-Futura-u35 Linotype-Futura-u55 Linotype-Futura-u56 Linotype-Futura-u75 Linotype-Futura-u76 ... For 2-part names, the "cut" is really what the font would be called anyway under current TeX conventions, and so combines the and in 3-part names. 1-part names are like current TeX names. > I don't see any advantage in limiting font names to three components. My scheme isn't supposed to classify every aspect of fonts in their names (not useful IMO) but to help divide the huge namespace of possible fonts into useful chunks: all Adobe fonts -- further subdivided into Helvetica (further subdivided into r, o, b, bo) Times (further divided into r, i, b, bi, sy) ... all Linotype ... all Bitstream ... ... all pdc ... misc //- Damian Cugley ---------------------------------------------------\ || Oxford University Computing Laboratory, 11 Keble Rd, Oxford, UK || || pdc@prg.ox.ac.uk or pdc@uk.ac.ox.prg in UK DON'T PANIC! || \-------------------------------------------------------------------//