Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!uokmax!alliant.backbone.uoknor.edu!jay
From: jay@alliant.backbone.uoknor.edu (Jay Liang)
Newsgroups: comp.sys.alliant
Subject: Troff/Transcript
Keywords: troff, transcript, C/A/T
Message-ID: <1990Dec3.172047.15708@uokmax.ecn.uoknor.edu>
Date: 3 Dec 90 17:20:47 GMT
Sender: news@uokmax.ecn.uoknor.edu (Nets)
Reply-To: jay@alliant.backbone.uoknor.edu (Jay Liang)
Organization: University of Oklahoma, Norman, OK
Lines: 17
Originator: jay@alliant.backbone.uoknor.edu


     After playing around troff with the Adobe Transcript
(version 2.1) I concluded that the troff provided from Alliant does
not work correctly.  Here is what I did: I used troff with the Adobe
fonts to generate the C/A/T files and transferred them to a non-Alliant
machine and piped them through pscat and got the same results as I
got from the Alliant.  When reversing the process, using the C/A/T
files from the non-Alliant machine and used the pscat on the Alliant,
I obtained the correct output.  The problem was the character spacing.
The Alliant troff messed up the spacing.  Another supporting evidence:
enscript works fine on the Alliant which does NOT use troff in the
process.  Is there anybody know how I can fix this problem?  Alliant
Customer Support told me as what the man pages indicated that troff
was unsupported.  Thanks in advance.
-- 
Jay Liang                |   University of Oklahoma   |   (405) 325-5540
jay@alliant.uoknor.edu   |   jay@uokmax.uoknor.edu    |   chinet!uokmax!jay