🚀 go-pugleaf

Don't be misled by "spaceman's" comments.

Dov Isaacs, a very knowledgeable Adobe spokeperson posted in the thread that Adobe is working on the issue:

"If you know anything about PostScript, you must know that there is nothing simple about PostScript. There apparently is some code output from our Core Technology PostScript engine that is checking some type of variable in the current state of the print device that is making some assumption that just isn't correct for this particular PostScript implementation. To be very clear about this, the people who write this code at Adobe are very knowledgable engineers who I highly respect. It is not a case of "they couldn't get to the bottom of what seems to be a simple issue." That implies that they tried, couldn't find the problem, and gave up. That is not the case! The bug report is open and under investigation.

"Sorry to hear that you don't trust the PDF workaround. On the other hand, if you are proofing "seps" for an imagesetter via output to a LaserJet 4M, you may be deluding yourself in terms of how faithful those proofs are to what you will get on any particular imagesetter."

Here's the thread in full:

 <http://www.adobeforums.com/cgi-bin/webx?128@@.3bbcd8de>