Path: utzoo!attcan!uunet!lll-winken!sun-barr!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ANDREW.CMU.EDU!jaap+ From: jaap+@ANDREW.CMU.EDU (Jaap Akkerhuis) Newsgroups: comp.soft-sys.andrew Subject: Re: Printing ez documents (again) Message-ID: Date: 24 Oct 89 19:51:44 GMT References: <3578@daimi.dk> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 26 > Excerpts from mail: 24-Oct-89 Printing ez documents (again) Thomas > Rohde@uunet.uu.ne (691) > The included postscript uses two commands, > PB and PE, surrounding the actual code, which aren't defined in the > resultin postscript > file. I suppose they are doing some kind of setup. If my asumptions are > correct, > would someone mail me the missing code (if it isn't copyrighted.) The PB and PE postscript commands are indeed doing some setup. This is the way psdit program handles inbedded postscipt in the troff stream. And yes, this code is copyrighted since psdit and associated postscript code comes with the TranScript package from Adobe Inc. The code won't do you that much good anyway, since it depends also on the prologue as used by psdit. The only advise I can give is that you should consult your documentation for tpscript to find out whether they have a way to push raw postscipt through troff. If so, they are bound to have some setup commands as well. We don't have tpscript here, so I'm afraid that you are on your own on this one. If you get it to work, send your results, so other users of tpscript might use it. Good luck and happy postscript hacking. jaap