Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ukma!husc6!bochner From: bochner@flare.harvard.edu (Harry Bochner) Newsgroups: comp.lang.postscript Subject: Re: Seeking Laserprep 5.2 Message-ID: Date: 11 Dec 89 22:32:44 GMT References: <6365@cbnewsh.ATT.COM> <17412@rpp386.cactus.org> Sender: news@husc6.harvard.edu Distribution: usa Organization: Aiken Computation Lab, Harvard University Lines: 23 In-reply-to: woody@rpp386.cactus.org's message of 7 Dec 89 13:17:21 GMT In article <17412@rpp386.cactus.org> woody@rpp386.cactus.org (Woodrow Baker) writes: I don't mess with the mac world, but it is my understanding that there is a combination of key strokes something like Apple O or F that will cause the Postscript printer output to be redirected to a file. It will include the preamble. The file should be just what would be sent to the printer, and thus if you have laserprep, it should be pre-appended. Perhaps some one on the net knows the exact key strokes and methods. Hope this helps. command-F causes the postscript that would normally be sent to the printer to be saved in a file, but this is on the assumption that LaserPrep has already been downloaded. command-K saves everything, including all the initialization. Unfortunately, this tends to need some doctoring before it's appropriate for a non-Mac environment, since LaserPrep assumes that it should retain control for the remaining print jobs, and this mostly likely isn't what you want for a Unix environment. In the file that we have for AppleDict version #68 (which I think comes from LaserPrep 5.2), we have 10 lines commented out, starting after %%BeginProcSet, plus one more, beginning '/ok{statusdict ...'. Harry Bochner bochner@endor.harvard.edu