Xref: utzoo comp.lang.postscript:7211 comp.text.tex:4695 Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!att!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!usenet.INS.CWRU.Edu!daves From: daves@curie.ces.CWRU.Edu (Dave Stoutamire) Newsgroups: comp.lang.postscript,comp.text.tex Subject: Re: looking for dvi-to-postscript converter Message-ID: Date: 7 Jan 91 19:31:14 GMT References: <1991Jan6.145603.1781@dm.unibo.it> Sender: news@usenet.ins.cwru.edu Organization: Case Western Reserve University Lines: 33 In-Reply-To: fischer@iesd.auc.dk's message of 6 Jan 91 20:57:21 GMT Nntp-Posting-Host: curie.ces.cwru.edu In article fischer@iesd.auc.dk (Lars P. Fischer) writes: >>>>> On 6 Jan 91 14:56:03 GMT, ozalp@dm.unibo.it said: ozalp> is there a public domain dvi-to-ps converter that can handle ozalp> gf/pk fonts AND \special requests for inclusion of postscript ozalp> source in latex documents (eg. via psfig)? dvips by Tomas Rokicki (rokicki@neon.stanford.edu) is the one to use. The fact that Knuth himself hacked it to support virtual fonts is evidence enough for me. It's available in many places. labrea.stanford.edu is one. Works nicely with all kinds specials, PostScript fonts, etc, etc. I have the same problem, and dvips does not seem to solve it. psfig 1.2 generates the /special "pstext" which dvi2ps can handle but dvips cannot. This is a big problem, because for whatever reasons, dvi2ps does not always generate PS which our ALWs can print... comments like %%EOF are part of the problem, but I cannot figure out what else is going wrong. dvialw does work better, but it cannot handle the "pstext" /special either. Can anyone help? "psfig" is very nice, but this printing business is brain-death in action. -- daves@alpha.ces.cwru.edu | David Stoutamire, | gradual student of Computer Engineering (216) 368-5038 | at Case Western Reserve University