Article View: adobe.postscript.programming
Article #868Re: Adobe CPSI
From: Dov Isaacs
Date: Fri, 19 Sep 2003 17:59
Date: Fri, 19 Sep 2003 17:59
13 lines
3072 bytes
3072 bytes
OK, that's quite a mouthful, but let's start. (1) To take your "PS" first ... "creating a PostScript file and distilling" does NOT make a more reliable PDF than any other method. This is especially true with regards to InDesign's "Export PDF" function which produces highly reliable PDF. InDesign's exported PDF is fully compliant with the PDF 1.3 or 1.4 specification, depending upon the version of PDF you have specified for export! (2) You appear to be confusing a PostScript driver with a PostScript interpreter. A PostScript driver CREATES PostScript for subsequent interpretation by a PostScript interpreter. CPSI is one of a number of versions of PostScript interpreters licensed by Adobe to its OEMs including Heidelberg. The OEM "configures" CPSI to match the device characteristics of their hardware imagesetter, digital press, wide-format printer, etc. (3) CPSI is not a PDF interpreter; it is a PostScript interpreter. OEM products based upon CPSI that claim to interpret PDF actually first generate PostScript from the PDF using either a "PDFtoPS" component from Adobe or something similar of their own based upon a PDF Library. Thus, CPSI would not directly be the cause of any problem in interpretation of PDF exported by InDesign 2. If you are getting PostScript errors from a CPSI-based RIP from InDesign 2-exported PDF, it is because there is a problem in the creation of PostScript from PDF, not in CPSI itself. (4) Our OEMs' products that provide PDF support must have the latest upgrades and updates to support the versions of PDF that you are exporting from InDesign or Illustrator or for that matter, create with Acrobat Distiller. A PDF 1.4 file with live transparency exported from InDesign 2 will fail with a PDF workflow system that only supports PDF 1.3 and less. If such a system does allegedly support PDF 1.4 and you are getting failures with a PDF 1.4 file exported from InDesign, you should contact the system provider immediately. They are responsible for supporting you, not Adobe. It may be that they have some serious problem with the code they add to the system, modifications they may have made to Adobe code, or in fact your problem can be traced to a bug in Adobe code in which case, they will follow through and get a fix from Adobe. Hopefully, that helps explain this a bit. Please advise if you need further explanation. - Dov
Technical Details
Message-ID:
<2ccd7874.3@webx.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-09!supernews.com!news.maxwell.syr.edu!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!webxReferences:
<2ccd7874.-1@webx.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10c61a,108257f6e9f87d7e X-Google-Attributes: gid10c61a,public X-Google-ArrivalTime: 2003-09-19 11:07:56 PST From: "Dov Isaacs" <isaacs@adobe.com> Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-09!supernews.com!news.maxwell.syr.edu!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!webx Newsgroups: adobe.postscript.programming Subject: Re: Adobe CPSI Message-ID: <2ccd7874.3@webx.la2eafNXanI> Date: Fri, 19 Sep 2003 10:59:58 -0700 References: <2ccd7874.-1@webx.la2eafNXanI> Lines: 42 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit