[
https://issues.apache.org/jira/browse/PDFBOX-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307168#comment-14307168
]
Andreas edited comment on PDFBOX-2659 at 2/5/15 12:54 PM:
----------------------------------------------------------
The differences (I could spot) between invoice_patched and invoice_converted
are the following:
the converted one has extended XMP metadata entries and also an Outlines entry
under Catalog.
The thing I noticed though, is that the document actually has a Conformance
entry of level A. The OP hasn't stated how Preflight is being used. The default
facility via Validator_A1b obviously validates based on a Conformance level of
B. Validating the patched one against
www.pdf-tools.com/pdf/validate-pdfa-online.aspx reports the following:
Validating file "invoice_patched.pdf" for conformance level pdfa-1a
There is only one RDF resource allowed in XMP.
The document does not conform to the requested standard.
The document's meta data is either missing or inconsistent or corrupt.
Done.
I also took a look at the Preflight code yesterday. I cannot really tell if any
checks specific to Conformance level A are executed if one calls
PreflightParser.parse(Format.PDF_A1A). Parsing invoice_patched.pdf with this
Format does not alter the validation output.
was (Author: andkyr):
The difference (I could spot) between invoice_patched and invoice_converted are
the following:
the converted one has extended XMP metadata entries and also an Outlines entry
under Catalog.
The thing I noticed though, is that the document actually has a Conformance
entry of level A. The OP hasn't stated how Preflight is being used. The default
facility via Validator_A1b obviously validates based on a Conformance level of
B. Validating the patched one against
www.pdf-tools.com/pdf/validate-pdfa-online.aspx reports the following:
Validating file "invoice_patched.pdf" for conformance level pdfa-1a
There is only one RDF resource allowed in XMP.
The document does not conform to the requested standard.
The document's meta data is either missing or inconsistent or corrupt.
Done.
I also took a look at the Preflight code yesterday. I cannot really tell if any
checks specific to Conformance level A are executed if one calls
PreflightParser.parse(Format.PDF_A1A). Parsing invoice_patched.pdf with this
Format does not alter the validation output.
> Dublin Core: Title not defined
> ------------------------------
>
> Key: PDFBOX-2659
> URL: https://issues.apache.org/jira/browse/PDFBOX-2659
> Project: PDFBox
> Issue Type: Bug
> Components: Preflight
> Affects Versions: 1.8.8
> Reporter: Marcus Ilgner
> Priority: Minor
> Labels: pdf/a
> Attachments: PDFBOX-2659.diff, invoice_converted.pdf,
> invoice_old.pdf, invoice_patched.pdf, pdf1a.xml
>
>
> Validating a PDF for A1 compatibility, I get an error:
> {quote}
> Error on MetaData, Title present in the document catalog dictionary can't be
> found in XMP information (Property is not defined)
> {quote}
> Yet when I look at the file, the property is defined as such:
> {code}
> <dc:title>
> <rdf:Alt>
> <dc:li>Rechnung 14512-14-001</dc:li>
> </rdf:Alt>
> </dc:title>
> {code}
> The code that sets the title (in order to make sure it's the same as the one
> from the document information):
> {code}
> DublinCoreSchema dublinCore = xmp.createAndAddDublinCoreSchema();
> dublinCore.setTitle("x-default", docInfo.getTitle());
> {code}
> Setting the creator via DublinCoreSchema seems to work as it doesn't raise
> the error anymore after calling
> {code}dublinCore.addCreator(docInfo.getAuthor());{code}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
