Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!sun-barr!lll-winken!gauss.llnl.gov!casey
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: Re: gwm Docs (Postscript inclusion)
Message-ID: <42989@lll-winken.LLNL.GOV>
Date: 3 Jan 90 21:23:59 GMT
References: <1990Jan3.142041.4758@ux1.cso.uiuc.edu> <479@mirsa.inria.fr>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: casey@gauss.llnl.gov (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 28

| From: colas@crios.inria.fr (Colas Nahaboo)
| 
| > From: garyf@mehlville.ncsa.uiuc.edu (Gary Faulkner)
| > 
| > I picked up the gwm-1.5.1.5.ps.Z file (supposedly the documentation in 
| > postscript format).  I have been unable to print it on any of our
| > printers.
| 
| There seem to be a problem with the inclusion of xwd|xpr -device ps file
| in LaTeX (yet it prints here on all of our printers...)

  One of the problems I noticed is that you are apparently using the
dvi2ps that comes with the TeX distribution.  (It's not your fault, it's
the only public domain DVI to PS conversion program I know about.)  That
version of dvi2ps is terrible.  (Pierre MacKay is working on getting a
better version but I haven't heard anything about that project for the
last four months.)

  The fundamental problem with dvi2ps seems to be that the PostScript
output that it generates seems to allocate memory in the printer for each
page, but fails to free it at the end of the page.  Hence the syndrome
often seen with dvi2ps where you may not be able print an entire
document, but are able to print it out in sections.

  I used ArborText's dvips program and didn't have any problems.
Unfortunately ArborText is a pay for play product ...

Casey