Xref: utzoo comp.lang.postscript:7207 comp.text.tex:4668
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!bloom-beacon!deccrl!news.crl.dec.com!tuttle
From: tuttle@crl.dec.com (Mark R. Tuttle)
Newsgroups: comp.lang.postscript,comp.text.tex
Subject: Re: looking for dvi-to-postscript converter
Message-ID: <1991Jan7.201627.28734@crl.dec.com>
Date: 7 Jan 91 20:16:27 GMT
References: <1991Jan6.145603.1781@dm.unibo.it>
	<FISCHER.91Jan6205721@thiele.iesd.auc.dk>
	<DAVES.91Jan7143114@curie.ces.CWRU.Edu>
Sender: news@crl.dec.com (USENET News System)
Organization: DEC Cambridge Research Lab
Lines: 20
In-Reply-To: daves@curie.ces.CWRU.Edu's message of 7 Jan 91 19:31:14 GMT

In article <DAVES.91Jan7143114@curie.ces.CWRU.Edu> daves@curie.ces.CWRU.Edu (Dave Stoutamire) writes about dvips and psfig not working well together:

   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.

Here at work, I've installed the psfig/tex 1.2 implementation I pulled
off linc.cis.upenn.edu on 10/5/90.  This distribution seems to contain
three implementations of the psfig macros: one for dvips, one for
dvi2ps by Stephan Bechtolsheim, and one for dvi2ps by Tony Li.  I have
no trouble using dvips and the dvips implementation of psfig.  If I
remember correctly, if I try to use dvips and one of the dvi2ps
implementations of psfig, then dvips complains about not understanding
the "pstext" appearing in the \special's generated by the \psfig
command.

Mark Tuttle
tuttle@crl.dec.com

Standard disclaimers apply.