Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!cs.utexas.edu!sun-barr!newstop!sun!exodus!appserv!angel.Eng.Sun.COM!henry From: henry@angel.Eng.Sun.COM (Henry McGilton) Newsgroups: comp.lang.postscript Subject: Re: Getting Transcript 2.1 to use all LaserWriter Fonts Summary: Relentless Message-ID: <446@appserv.Eng.Sun.COM> Date: 19 Feb 91 00:51:09 GMT References: <*fcG4w.k@cs.psu.edu> <1398@vidiot.UUCP> <1406@vidiot.UUCP> Sender: news@appserv.Eng.Sun.COM Lines: 29 In article <1406@vidiot.UUCP>, brown@vidiot.UUCP (Vidiot) writes: * The II NTX printer is the unit with a hard disk, * if I remember correctly, since I have the II NT. * Because of the hard disk, more font families can * be resident, non of which are covered by TranScript. To the best of my admittedly minuscule knowledge, there is nothing intrinsic to TranScript that will prevent TranScript, or more precisely, troff and pscat, from working with any font family you desire. For old troff to correctly format a document using a given font family, it needs width tables which pscatmap generates from AFM files. pscat needs a correspondence file to map character codes to PostScript strings. pscatmap builds this correspondence file also. That's all there is to it -- there are no fonts `built into TranScript'. troff can access any fonts, with the understanding you obtain or create AFM files so pscatmap can generate tables for troff and pscat, and old troff can only mount four fonts. I omit the case of eight-font C/A/T troff. TranScript has no notion of printer-resident fonts, downloaded fonts, disk-resident fonts, or indeed, any idea how to download a font. TranScript doesn't `cover' fonts at all -- it's just a translation/communication service. I hope the original requestor obtained the information he requested because we'be drifted (too far) off the topic. ........ Henry