Path: utzoo!attcan!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: 30 Sep 89 13:30:25 GMT References: <860@pacific.mps.ohio-state.edu> <4776@cps3xx.UUCP> <4793@cps3xx.UUCP> Sender: spqr@ecs.soton.ac.uk Organization: Southampton University Computer Science Lines: 21 In-reply-to: smithda@cpsvax.cps.msu.edu's message of 29 Sep 89 19:09:00 GMT Since the message about dvi->ps features a few days ago, this is the third dvi->ps program I've heard about. The point of my orginal message was to get rid of all these dvi->ps translators and have just ONE dvi2ps with all the features that everybody wants. I listed a few but if there is already a program that does all you want, there is no problem left, is there? But to be serious, I think the discussion is premature, until the TUG committee for standards in drivers releases its final report; they have been brooding over features that ALL drivers should have, and when we know what that definitive list is, it won't matter how many dvi->ps drivers there are, so long as they all conform to the minimum requirements. They would eventually coalesce, because no-one would bother to write new ones. The reason why we currently have 157 dvi to PS programs (we're only running about 5 at this site on various machines, so we're not up to much) is the lack of agreement on features - we only have one TFtoPL, because there is no doubt about what it is supposed to do. -- 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)