Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!sdd.hp.com!ucsd!ucbvax!ANDREW.CMU.EDU!tpn+ From: tpn+@ANDREW.CMU.EDU (Tom Neuendorffer) Newsgroups: comp.soft-sys.andrew Subject: troff and transcript Message-ID: Date: 27 Jul 90 16:37:24 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 18 > Wouldn't another *roff clone work as well? How's Transcript required? We have been trying to find a working version of c++ so we can try groff. I have no reason to believe that it wouldn't work, and would be very interested in hearing from anyone who has been able to try it. With regards to Transcript, the piece that ATK uses is the psdit program that takes the output of ditroff and translates it into postscript. I believe that all ditroff users who print on Postscript printers are using this package, whether they know it or not. Lpr is smart enough to call it when it is needed. If you are printing on non-postscript printers, then you don't need psdit, however, by the same token, you won't be able to print the ATK objects that generate postscript rather than troff. The most common objects that generate postscript are raster and the drawing editor zip. When these objects are embedded in text, or another object that generates troff, the postscript they generate is surrounded by some special macros so that troff leaves space for the drawing that is then passed through to the printer.