Re: Survey about use of Acrobat on the Mac
> {quote:title=Dov Isaacs wrote:}{quote}
> Just to make sure we are clear on terminology here ...
>
> When we discuss products with the +Adobe PDF Print Engine+, we are referring to products that are directly RIPing existing PDF, preferably directly created from layout and illustration software.
>
> The "PDF Print Engine" referred to by +bluskool+ has nothing to do with the +Adobe PDF Print Engine+, but rather, is Quark's description of software they license from Global Graphics that converts PostScript output by QuarkXPress into PDF in a manner similar to the way Adobe's Acrobat Distiller converts PostScript to PDF.
That is not at all what I was referring to. I am referring to the PDF printer that comes with Creative Suite 3. I print from quark using "Adobe PDF 8.0" as the printer to get my PDF's. I am not referring to the JAWS engine as you said.
> Another topic touched upon ... If you have a "poorly made PDF" whether from Publisher or whatever, rasterization in Photoshop is the best way to ruin it further!
This is what gets us frustrated in the printing world. Just yesterday I needed to convert a poorly made PDF from RGB to CMYK. I did it first in Acrobat and ended up with big blocks of patterns around all of the Letters on the cover. I opened it in Photoshop (at a resolution of 900 which keeps it from being ruined as you have said), converted the colors, saved as EPS and distilled. A directly made PDF was over 200MB. The PDF I got via the EPS and distill method was under 1MB.
> If Photoshop can rasterize it, then any current Adobe product should be able to open it and the Adobe RIP-based products (whether CPSI or Adobe PDF Print Engine) should be able to RIP it. The components used in Photoshop are really no different than what is used in the rest of Adobe's products.
This is incorrect as I have pointed out. Acrobat failed to do what Photoshop could.
>And even then, if you want to create a PDF file from Photoshop, Adobe recommends that you directly save as PDF from Photoshop. There is no good reason to create PostScript and distill it in this case. What are you afraid of?
I am afraid of waiting for an hour to upload a file to the printers server when it could take 30 seconds. The real question is "is there any good reason to directly export it?" What is the good reason for wanting a 200MB file, when all that is needed is a 1MB file? Why does Photoshop include so much unnecessary information in the PDF's it produces? I have shed over 50MB from a PDF directly exported from Photoshop just by removing application data and metadata from the file.
You guys have got to realize that your ambition is exceeding practicality right now. I fully support moving entirely away from postscript. I love the fact that you guys are creating technology that moves us away from postscript and gives us a better, more reliable way to predict the final outcome, but the technology is not there yet.
Why was Photoshop able to "fix" that PDF I was referring to when I could not fix it in Acrobat? I would be glad to send the file to you. It is just one of countless examples. As far as I know, opening it in Photoshop was the only way to get the colors to convert to CMYK without damaging the appearance of the document. If there is a another, better way that you know about, please demonstrate. Just saying that Photoshop will render PDF's the same as every other CS3 app does not make it so.
Dan R.
PS don't take this the wrong way. I am little annoyed, but I still have mad love for Adobe products. In fact if everyone in the print world only used CS3 apps, the problems I am discussing would not exist. The problem is that we have to deal with graphics created in other programs.