🚀 go-pugleaf

In article <257@heaven.woodside.ca.us> glenn@heaven.woodside.ca.us
(Glenn Reid) writes:

> The Macintosh already downloads machine code, which is also one of the
> reasons that Mac-generated PostScript files run into trouble on other
> brands of printers.  There is "bit-smoothing" code in eexec form buried
> in LaserPrep (or was the last time I looked).  Luckily, it checks to see
> if the product is an Apple LaserWriter before executing it.  Unluckily,
> in the process of NOT executing it, it often NOT executes the rest
> of your job too.  Adobe's driver should fix this, I would imagine.  In
> the meantime it continues to be a first-class headache for everyone trying
> to use Mac-generated PostScript.  In fact, I'm sure it's one of the most
> frequently asked questions in this newsgroup.

For the record, the "flushfile"s were replaced with code that reads up to a
known %-comment in level 6.0 (dict version 70) printing.  The problem Glenn
alludes to is present in 5.0 and 5.2 printing.  When doing my vetted versions
I replaced the flushfiles with painstakingly-counted skip-counts, like that
used to skip the LaserWriter II NT retrofit code near the top.

There are other gotchas that are still there.  Look for calls to
"setsccinteractive", "waittimeout", and "setdefaulttimeouts".

Or get "macps" from sumex, run it on a command-K file, then diff it :-)

-- 
Ben Cranston <zben@umd2.umd.edu>
A determined iconoclast, it would be better to assume the opinion expressed
above is the diametric OPPOSITE to that of the Warm and Fuzzy Network Group
of Egregious State University...