Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!uw-beaver!ubc-cs!kiwi!zaphod.mpr.ca!parker
From: parker@zaphod.mpr.ca (Ross Parker)
Newsgroups: comp.unix.questions
Subject: Re: printing postscript files
Message-ID: <2063@kiwi.mpr.ca>
Date: 20 Feb 90 01:58:37 GMT
References: <1990Feb19.155338.8914@druid.uucp> <6461@cps3xx.UUCP>
Sender: news@eric.mpr.ca
Reply-To: parker@zaphod.mpr.ca (Ross Parker)
Distribution: na
Organization: Microtel Pacific Research Ltd. (MPR)
Lines: 32

In article <1990Feb19.155338.8914@druid.uucp>, darcy@druid.uucp (D'Arcy
J.M. Cain) writes:
> In article <6461@cps3xx.UUCP> davisd@cpsvax.cps.msu.edu (Dug) writes:
> >Hi,
> >  I was wondering if anyone out there prints Mac generated postscript
> >files using Unix.  I've been trying with no luck.  Here's what I do:
. . .
> I'll ask the stupid question first.  Do you actually have a PostScript
> printer attached?
> The printer may have been set up
> to  emulate some other sort of printer such as a QMS with the switch
> set to Diablo mode.  The other possibility is that the default printer
> is filtered through an ASCII printer emulator
> 

Actually, the most likely possibility is that you aren't including
the correct (or any) postscript header file with the Mac-generated
postscript. I believe the command-K sequence generates a file that
includes lots of non-existant postscript commands, and doesn't start
with the '%!' magic cookie that Transcript software (from Adobe)
looks for.

This usually works on a Mac, because the printer has been pre-loaded
with the necessary functions. Printers hung off UNIX systems are
rarely set up this way.

I believe there's some magic Mac keystroke sequence or something that
will magically generate a header file for you, but (not being a Mac
hack) I can't help you with that one! Anyone else?

Ross Parker				parker@mpre.mpr.ca
(604)293-5495				uunet!ubc-cs!mpre!parker