jesperse@wk18 (Dennis C. Jespersen) (02/25/89)
I've got TeX and Metafont running on a NeXT machine; the installation was fairly easy, using the source files from ics.uci.edu (web sources and web-to-C-ware) and labrea.stanford.edu (other TeX- and Metafont-ware). I was interested in generating some 400 dpi fonts for the NeXT printer (I had some 300 dpi fonts available which we use on an Apple LaserWriter.) The Metafont parameters I came up with after some experimenting were: blacker=0.75; fillin=0; o_correction=0; (generating cmr10 at 300dpi with these parameters gave a font that matched the "given" 300 dpi font pixel-for-pixel except for one character). Then I tried cmr10 at 400dpi with these settings. A comparison of the font tables at 300 dpi and 400 dpi (from the "testfont.tex" file) shows the 400 dpi font is much improved over the 300 dpi font. The quality of the 400 dpi font is really very good; the printer is impressive. Generating a full set of Computer Modern and LaTeX fonts (93 fonts) takes about 2.5 hours of processing time on the NeXT. After packing to pk format, the collection of pk files at magsteps 0,1,2,3 occupies 623, 753, 918, 1125 Kbytes respectively. The dvi-to-PostScript driver I'm using is based on Beebe's dvialw; some hacking was necessary to get it to produce correct 400 dpi output, as it seems there are a few places in the code where the assumption is made that the only possible output resolutions are 200, 240, or 300 dpi. --Dennis Jespersen jesperse@wk18
UH2@PSUVM.BITNET (Lee Sailer) (02/27/89)
In article <1515@amelia.nas.nasa.gov>, jesperse@wk18 (Dennis C. Jespersen) says: > >I've got TeX and Metafont running on a NeXT machine; the installation >was fairly easy, using the source files from ics.uci.edu (web sources and >web-to-C-ware) and labrea.stanford.edu (other TeX- and Metafont-ware). ... >Generating a full set of Computer Modern and LaTeX fonts (93 fonts) >takes about 2.5 hours of processing time on the NeXT. After packing to >pk format, the collection of pk files at magsteps 0,1,2,3 occupies xxx3, 753, 918, 1125 Kbytes respectively. > >jesperse@wk18 Good man. It occurs to me that someone, or even NeXT, could save us all a lot of wasted time by collecting the currently available font library for TeX, doint the 400dpi and screen versions (90dpi? 100dpi?) and ...I know! put it on a od cartridge and release it to the public domain! lee
greid@adobe.com (Glenn Reid) (03/01/89)
In article <73465UH2@PSUVM> UH2@PSUVM.BITNET (Lee Sailer) writes: >In article <1515@amelia.nas.nasa.gov>, jesperse@wk18 (Dennis C. Jespersen) says: >> >>I've got TeX and Metafont running on a NeXT machine; the installation >>was fairly easy, using the source files from ics.uci.edu (web sources and >>web-to-C-ware) and labrea.stanford.edu (other TeX- and Metafont-ware). > ... > >>Generating a full set of Computer Modern and LaTeX fonts (93 fonts) >>takes about 2.5 hours of processing time on the NeXT. After packing to >>pk format, the collection of pk files at magsteps 0,1,2,3 occupies >xxx3, 753, 918, 1125 Kbytes respectively. >> >>jesperse@wk18 > > >Good man. It occurs to me that someone, or even NeXT, could save us all >a lot of wasted time by collecting the currently available font library >for TeX, doint the 400dpi and screen versions (90dpi? 100dpi?) and >...I know! put it on a od cartridge and release it to the public domain! You could always just scrap the Computer Modern fonts and use PostScript fonts? The NeXT machine uses the Display PostScript system, which means you might not need tons of 400dpi bitmaps when you can use outline fonts instead. Perhaps this has already occurred to you and you have ruled it out for other reasons, but I thought I should point it out, at least. The availability of higher- and higher-resolution devices is one of the main arguments against bitmap fonts. Look at all the time, space, and hassle they require so support a new printer (it looks like about 3 megabytes for a single font set). Not to mention the differences between write-white and write-black engines, etc., etc. Glenn Reid Adobe Systems
tli@sargas.usc.edu (Tony Li) (03/02/89)
In article <73465UH2@PSUVM> UH2@PSUVM.BITNET (Lee Sailer) writes:
Good man. It occurs to me that someone, or even NeXT, could save us all
a lot of wasted time by collecting the currently available font library
for TeX, doint the 400dpi and screen versions (90dpi? 100dpi?) and
...I know! put it on a od cartridge and release it to the public domain!
Or..... Just tar it up and put it in one of the archives.
Tony Li - USC University Computing Services - Dain Bramaged.
Uucp: oberon!tli
Bitnet: tli@kylara, tli@ramoth
Internet: tli@sargas.usc.edu