Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!romp!auschs!d75!woan
From: woan@nowhere (Ronald S Woan)
Newsgroups: comp.unix.aix
Subject: Re: troff -t on AIX3.1?
Message-ID: <3781@d75.UUCP>
Date: 16 Apr 91 17:24:55 GMT
References: <1991Apr15.202022.14455@dartvax.dartmouth.edu> <3775@d75.UUCP> <1991Apr16.132006.1015@dartvax.dartmouth.edu>
Sender: news@d75.UUCP
Reply-To: woan@cactus.org
Organization: Austin School of Hardknocks
Lines: 22

In article <1991Apr16.132006.1015@dartvax.dartmouth.edu> paw@eleazar.dartmouth.edu (Pat Wilson) writes:
>Well, you're right that "troff filename" prints to stdout, so perhaps
>I can use this as a workaround.  Most troff's that I'm familiar with
>(and that documented in the BSD manuals) output to the
>"phototypsetter" *unless* one uses the -t option to divert to stdout.
>Maybe the way it's done here makes more sense, but it's _not_ the way
>it's historically been done, which is a bit annoying when you're in a
>heterogenous environment...

All ditroffs that I have seen behave this way, so you will encounter
this more and more as the old CAT troffs are retired. Anyway, blame it
on AT&T or else buy their DWB for all of your systems and then they'll
all behave this way... :-)

This is nothing compared to when I went from the old awk to nawk and
had to start figuring out what the incompatibilities that were killing
off my old scripts were...
--
+-----All Views Expressed Are My Own And Are Not Necessarily Shared By------+
+------------------------------My Employer----------------------------------+
+ Ronald S. Woan                woan@cactus.org or woan@austin.vnet.ibm.com +
+ other email addresses             Prodigy: XTCR74A Compuserve: 73530,2537 +