Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!uc!uh.msc.umn.edu!jps
From: jps@uh.msc.umn.edu (Jeff P. Sorvik)
Newsgroups: comp.text.desktop
Subject: Re: Any good WYSIWIG desktop publishing software on UNIX
Message-ID: <2135@uc.msc.umn.edu>
Date: 13 Jul 90 13:15:57 GMT
References: <1990Jul12.125922.22444@DRD.Com> <269CF99C.58B4@intercon.com>
Sender: news@uc.msc.umn.edu
Reply-To: jps@msc.umn.edu
Organization: Minnesota Supercomputer Center
Lines: 30

In article <269CF99C.58B4@intercon.com>, amanda@mermaid.intercon.com
(Amanda Walker) writes:
> In article <1990Jul12.125922.22444@DRD.Com>, mark@DRD.Com (Mark Lawrence)
> writes:
> > In interleaf, you can't get hold of this PS file -- a daemon
> > takes over the whole process of printing to Ileaf's intefmediate file,
> > converting it to PS, then sending it to the printer.
> 
> Yow.  That certainly renders it useless to us.
> 
> We did our last manual in LaTeX, but there's growing pressure to go to
> something more-or-less WYSIWYG; evidently the rest of the company isn't as
> strong on the form/content distinction as I am...
> 
> However, whatever we use, it is quite important for us to be able to
> generate a PostScript file that we can send offsite for typesetting.
> 

Sorry to burst the bubble, but you CAN get access to the postscript file
in Interleaf.  You just redirect the intermediate file to a file rather than
a device.  You can then create a shell script that puts the "printerleaf" file
through the postscript converter they supply and either send it to a printer
or just keep the postscript file.

We do that all the time here.  That way I can send a postscript file to other
sites electronically and allow them to print them rather than mailing an 
entire bulky manual using the Postal Service.

- Jeff Sorvik
(Minnesota Supercomputer Center)