Aandi Inston
To re-create the situation: To start off we are a newspaper that received an ad in that was originally created with Adobe Indesign CS, when this ad was sent to us - it was converted to a PDF, which then converted the fonts to Double-Byte, Identity-H, or Composite - whatever you would like to call them.
When the ad comes in, we first run a Pitstop Certification, which usually gets the ad to a final point for output. The ad then gets EPS'd from Acrobat, placed on a Quark Document (V5), then if changes or modifications are done in Quark, then it gets EPS'd from there to our OPI server, then placed in our Editorial System.
When we output the Editorial pages, all pages are usually converted to a PDF before being sent to our Harlequin (Eclipse Release) rips.
The problem I'm running into, is when the final page is being PDF'd through Acrobat 6.0 or 6.1 and then sent to the rip... it fails on the RIP, with the "StartData" error message, which usually means a corrupt font or something similar. If I take the original ad off the page and re-distill, then re-output the PDF it works fine OR if I take the Postscript file which is created before the PDF is made, with the ad on the page, the page rips fine. One LAST step I tried, is taking the page (with the ad again) - and running it through Acrobat 5.0 - the PDF then rips fine, along with the Composite Fonts.
To me, this means, something different is happening with double-byte fonts in Acrobat 6 compared to Acrobat 5. Please let me know if anybody might have an ideas with Acrobat Distiller 6 creating the problem, I have tried turning on/off almost every setting in Distiller 6, without luck.
Thanks,
Ron Kline