🚀 go-pugleaf

In article <6937@alice.UUCP> d@alice.UUCP (Daniel Rosenberg) writes:
>Help!
>
>I need to know if there is any way of capturing Postscript output
>from a Macintosh into a file. I'd like to take such a file, upload
>it to a VAX, and pump it out to a Postscript device.
>
> [...]
>-- 
># Daniel Rosenberg (CE) AT&T Bell Labs, Murray Hill
># disclaimer: These opinions are necessarily mine, not my employer's.     
># UUCP: {ihnp4 || research || allegra}!alice!d  AT&T: 201/582-6455 (work)
># INTERNET: d%alice%btl@csnet-relay or d@alice.att.com


I'm sure that lots of people have mailed Daniel the details of the
command-option-whatever hidden method for putting postscript into
a file.

This same information has been requested in this newsgroup at least
once a month.  I have seen it requested and answered in most Mac magazines.

I hope that the message has made it through to program developers -
document useful user interface characteristics in the user interface,
don't use command-option-stand-on-your-head tricks that are only
discoverable by reading the manual.  This send-output-to-a-file-instead
option should be either an option check-box in the print-setup menu,
or a postscript-into-text-file device driver that can be selected
with chooser.  Either of those methods would be discovered easily
by most of the people who request the info (and would probably have
been noticed even by people who had no idea that "printing to a file"
was a legitimate concept, much less possible to do).
-- 
---------  .signature eater food ---------
John Macdonald   UUCP:    {mnetor,utzoo} !spectrix!jmm
                 internet:Sorry. We're in range, but we're in no domain.
Disc-claimer: (noun) any hack's source directory