A Word document converted with Acrobat Pro 9.1.3 to PDF (without A) followed by a PDF/A-Conversion with Ghostscript results in a number of errors: - Syntax: Missing EOL after endobj German: Indirektes Objekt “endobj”-Schlüsselwort nicht nach “EOL”-Kennung Keine EOL-Kennung nach "endobj"-Schlüsselwort in einem indirekten Objekt - Syntax: incorrect length for data object folder German: Datenobjekt-Verzeichnis hat inkorrekten Längen-Eintrag - Syntax: incorrect format for data object folder German: Syntax-Problem: Datenobjekt-Verzeichnis inkorrekt formatiert - Comment has no flags German: Kommentar enthält keinen Flags-Eintrag - Comment is not set to "printing" German: Kommentar ist nicht auf druckend gesetzt Command used to create PDF/A: gswin32c.exe -dPDFA -dBATCH -dNOPAUSE -dNOOUTERSAVE -sFONTPATH=C:\WINDOWS\Fonts -dUseCIEColor -sProcessColorModel=DeviceCMYK -sDEVICE=pdfwrite -sOutputFile=aPDFtestOut.pdf PDFA_def.ps aPDFtest.pdf Using the same PDFA_def.ps as in Bug 690768 (resulting in additional errors not mentioned here)
Created attachment 5442 [details] aPDF2test.pdf (The file to convert to PDF/A)
Created attachment 5443 [details] aPDF2testOut.pdf (The converted file with PDF/A-errors)
Created attachment 5444 [details] aPDFtestOut_report.pdf (The PDF/A-error report by Acrobat Pro 9.1.3 Preflight)
Created attachment 5445 [details] aPDF2testOut_report.pdf (The PDF/A-error report by Acrobat Pro 9.1.3 Preflight) aPDF2testOut_report replaces aPDFtestOut_report
When converted to PDF/A using the current HEAD revision (and, I thought, 8.70) Ghostscript emits the following warning: Annotation set to non-printing, not permitted in PDF/A, reverting to normal PDF output. This was an enhancement made in July 2009 to prevent creation of non-compatible PDF/A files. See revision 9876, bug #690500 and the Ghostscript documentation gs/doc/ps2pdf.htm the new PDFACompatibilityPolicy switch. Unfortunately this new feature does not seem to be working correctly with your file, and the default is still attempting to produce a PDF/A file, apparently because the setting is reset on subsequent pages (initial testing was with a single page file). Are you certain you are using version 8.70 of Ghostscript, or did you simply miss the warning ? If I set -sPDFACompatibiltyPolicy=1 so that GS elides any non-conforming annotations then I can create a conforming PDF/A file.
revision 10141, patch here: http://ghostscript.com/pipermail/gs-cvs/2009-October/009865.html Correctly resets PDF/A production when encountering non-compliant input and the PDFACompatibiltyPolicy is 0 (produce regular PDF file) on multi-page input. Please note that in comment #5 -sPDFACompatibilityPolicy should instead read -dPDFACompatibilityPolicy. That is a -d switch not a -s switch.
Thank you very much. Using the parameter "-dPDFACompatibilityPolicy=1" solves all five PDF/A-errors mentioned in comment 1. The PDF-annotation (German: Kommentar, Notiz) is removed from the PDF/A-dokument (for PDF/A-compliance). The command used and the resulting Ghostscript output: gswin32c.exe -dPDFA -dBATCH -dNOPAUSE -dNOOUTERSAVE -sFONTPATH=C:\WINDOWS\Fonts -dUseCIEColor -sProcessColorModel=DeviceCMYK -sDEVICE=pdfwrite -dPDFACompatibilityPolicy=1 -sOutputFile=aPDF2testOut.pdf PDFA_def.ps aPDF2test.pdf GPL Ghostscript 8.70 (2009-07-31) Copyright (C) 2009 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 2. Page 1 GPL Ghostscript 8.70: Annotation set to non-printing, not permitted in PDF/A, annotation will not be present in output file