Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!ukc!icdoc!sot-ecs!spqr From: spqr@ecs.soton.ac.uk (Sebastian Rahtz) Newsgroups: comp.text Subject: Re: DVI files to Postscript (and tools) Message-ID:Date: 28 Sep 89 08:04:04 GMT References: <860@pacific.mps.ohio-state.edu> <4776@cps3xx.UUCP> Sender: spqr@ecs.soton.ac.uk Organization: Southampton University Computer Science Lines: 19 In-reply-to: smithda@cpsvax.cps.msu.edu's message of 28 Sep 89 01:18:57 GMT the following features were requested in a postscript driver for TeX 1 * GOOD PostScript output (I assume this also means fast PS output) 2 * Inclusion of other PS files (EPSF format). Since the output will 3 * Support of ALL font formats. I know PKs are the best, but we 4 * Support of Internal PostScript fonts. A naming standard needs to 5 * Support of other PS fonts. Both user defined fonts (so I can 6 * Font substitution. Substitute missing fonts with "close" fonts, 7 * I like the PS font scaling of Bitmaps mentioned above. 8 * Control over the PS encoding vector (so I can use those neat 9 * All options controllable from a file. A file like 10 * Correct VM memory usage. I should be able to print the PS file all but 3 and 7 are already in dvitops (not to be confused with dvi2ps, dvitps or dvips). Since I started to use it at the start of this year, I have seen no reason to return to the mad world of the everchanging dvi2ps versions -- Sebastian Rahtz S.Rahtz@uk.ac.soton.ecs (JANET) Computer Science S.Rahtz@ecs.soton.ac.uk (Bitnet) Southampton S09 5NH, UK S.Rahtz@sot-ecs.uucp (uucp)