Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!necntc!adelie!ora!tim
From: tim@ora.UUCP (Tim O'Reilly)
Newsgroups: comp.unix.questions,comp.text
Subject: Re: Troff - "Typesetter busy" message
Message-ID: <644@ora.UUCP>
Date: Thu, 30-Jul-87 09:00:13 EDT
Article-I.D.: ora.644
Posted: Thu Jul 30 09:00:13 1987
Date-Received: Sat, 1-Aug-87 11:52:20 EDT
References: <585@ritcv.UUCP> <643@ora.UUCP> <6196@brl-smoke.ARPA>
Organization: O'Reilly & Associates, Inc., Newton, MA
Lines: 34
Xref: mnetor comp.unix.questions:3418 comp.text:1009

In article <6196@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn ) writes:
> In article <643@ora.UUCP> tim@ora.UUCP (Tim O'Reilly) writes:
> >   troff -t -mx -Tsomedevice | postprocessor | lp -dsomedevice
> 
> This isn't right, at least for most implementations of troff.
> 
> Old (C/A/T) troff:
> 	troff -t -mx | cat-interpreter...

There are a number of postprocessors now available for
otroff that make it work with laser printers, much as I've
noted.  Tplus from Textware International, and cat2dit/devps
from Pipeline Associates come to mind.

> New (DI) troff:
> 	troff -Tdevice-name -mx | postprocessor...
> Many postprocessors handle spooling automatically so the user
> doesn't have to pipe into a spooler.

Many don't.  However, the caution should certainly be noted.
There is a lot of variation out there.

> Since -mx is actually an abbreviation for a filename, NOT an option
> (gross, isn't it?), it should follow all actual options.

I've never heard this one before.  This is not essential.  
I've intermixed my macro options with other options in all kinds 
of order with no apparent differences in effect.
-- 
Tim O'Reilly (617) 527-4210
O'Reilly & Associates, Inc., Publishers of Nutshell Handbooks
981 Chestnut Street, Newton, MA 02164
UUCP:	seismo!uunet!ora!tim      ARPA:   tim@ora.uu.net