Problem with PXT or Quark Passport and Rampage.

[sequoyah]

I usually do my own output from Preps to a SelectSet 7000 with Sar 600 RIP. But recently I sent out for direct to plate to a trade service shop that has Preps and Rampage. I provided the Preps Job file, a Preps Template with a 4 page flatwork signature and 3 Illustrator CS eps files plus a PXT produced ps file as job source files for Preps.

Initially, the Preps output would not rip on the Rampage. A process of elimination identified the PXT ps file as the culprit. They were able to get the job out by first rasterising the PXT ps file (I presume in the Rampage) and imposing the ripped tiff file.

Now the Quark file that produced the problem ps via PXT may have been originally a Passport file because when I went to save it it asked me to select a language, but it saved anyway (QX 6.5 mac). I need to do more of this type of output with this trade shop, so what I need help with is determining if the problem for the Rampage was the possible Passport origins of the file or something introduced by PXT. Are either of these two known to have issues with Rampage? I don't have much info on their Rampage, but can get it if it would help determine the problem.

Thanks,

Al Ferrari

[almaink]

After Quark 5 that PXT extension was flakey at best for exporting postscript. If your sending to RAMPage direct PDF export from Quark, is a better way IMO.

[mwc]

Contact the people that you are sending your files to...they should be more than qualified/happy to tell you what type of files to send them. BTW - PXT extension should not be used for Quark EPS's in a Rampage workflow...a PDF and/or the native files may be the best type of file to send in your situation.

[sequoyah]

OK thanks. So PXT and Rampage don't play nice together then. Evidently I confirmed that.