what's your o/s? - a vaguely remember a hotfix for Windows XP that fixed PDF drop out issues - it's a font-handling issue with Windows
If you provide the details of the error message that Distiller spits out, it might help provide some clues as to what's possibly going wrong in your current files. Also, which version of Acrobat, what joboptions were used, is the Adobe PDF printer instance the default for the FM session, etc., i.e. all of the usual suspects.
My OS is Windows XP. So maybe the hotfix may work. Can you provide more details?
The Acrobat version is 8.0. The Job Options are high quality print. Adobe PDF printer is the default for the session.
I don't see an error message when I run 'high quality print', the distiller runs normally it's just that the generated PDF has none of the formatting and is missing vast sections of content from the frame files. Same when I run "standard".
I see error messages when I try to create the PDF using the PDF/A-1b:2005 (CMYK) option. Here it is:
<PDFA ISO="19005-1:2005" COMPLIANT="false">
PDF/A Compliance Report
[Violation] The F key in the Annot dictionary is missing or has an invalid value.
Page 2, Occurrences: 4
Page 448, Occurrences: 68
Page 449, Occurrences: 48
Violations: The total found in this section was 1348.
Warnings: The total found in this document was 0.
Violations: The total found in this document was 1348.
This document does not pass PDF/A-1b:2005 compliance checks.
%%[ Warning: Did not pass PDF/A compliance tests.. No PDF file produced. ] %%
1 person found this helpful
Unless you're trying to create the archival versions of the PDF, don't use any of the PDF/A options. Use the joboptions specific for the type of deliverable required.
Since you're seeing dropouts, are these sections specific to any fonts that you're using? Also, check that your Distiller configuration is still pointing the locations on your system that contain the fonts you've used in the FM document. Distiller needs to have these explicitly set. It doesn't query the system for the font locations.
For an XP system, you need to have the MS hotfix installed that Jeff mentions. See: http://blogs.adobe.com/techcomm/2009/07/repost_hotfix_for_framemaker.html
Hi Jeff/ Arnis
The hotfix has worked.
Thank you both for your help and patience.