Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!know!daemon
From: C506634@UMCVMB.MISSOURI.EDU (Eric Edwards)
Newsgroups: comp.text
Subject: Re: troff for uncooperative systems
Message-ID: <20836@know.pws.bull.com>
Date: 3 Feb 91 22:30:00 GMT
Sender: daemon@pws.bull.com
Lines: 29
Approved: warren@pws.bull.com

In Message-ID: <1241@ecicrl.ocunix.on.ca>
          clewis@ferret.ocunix.on.ca (Chris Lewis) said:
>In article <20723@know.pws.bull.com> C506634@UMCVMB.MISSOURI.EDU (Eric Edwards)
>>I've come across a bunch of troff files that I would like to print out.
>>Unfortunately, I don't have a convienent Unix box with a laser printer.
>The simplest approach would be to
>    1) ensure that the remote unix machine has a troff of some sort.

        Got that.

>    2) ensure that the remote unix machine can print on HP's or
>       Postscript printers.

       No can do.  It outputs to CATFOR typesetters only.

>    3) run troff on the remote system and produce postscript or HPPCL.
>    4) put the result on a floppy (or, via network connection)
>    5) print it on your Laserwriters or the HP's.
>(2) is probably the hard part.  If the remote UNIX system has CAT troff,
>psroff (which I wrote) will produce postscript or HPPCL.  With psroff you
>wouldn't need to worry about the fonts either.

How portable is psroff?  Is there any hope that I could get it to compile under
CMS, MS-DOS, MacOS or AmigaDOS?
(in case you're wondering.  Yes, I do have a C compiler for CMS)

Eric Edwards: c506634 @    "The 3090.  Proof that by applying state of the
Inet: umcvmb.missouri.edu   art technology to an obsolete architecture,
Bitnet: umcvmb.bitnet       one can achieve mediocre performance."