[
https://issues.apache.org/jira/browse/PDFBOX-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283579#comment-14283579
]
Maruan Sahyoun commented on PDFBOX-2562:
----------------------------------------
Let me add some background to what [~jahewson] wrote:
A font being embedded to a PDF file may or may not have all of the information
from the original font file as only some parts of the original font file are
required within a PDF. Validating these requirements is done as part of the
PDF/A validator and reflected there.
Validating the font itself would mean to validate it against the font
specification e.g. TTF. Some of these are ISO standards some are not. For some
there are multiple specs which might bring some ambiguity.
As the font program embedded into the PDF does not have all the information
required by the spec extracting the information and running it against a full
font check would bring up a lot of errors which are valid from a fonts
perspective (as the font might not be complete) but is not from a PDF
perspective (as the font doesn’t need to have all information required in the
font spec). In addition validating the font without the context information
from the PDF might als be incomplete.
The same applies in principle to other embedded resources like images.
An architecture which does a full validation of PDF and all embedded resources
would likely
- take a PDF
- validate the PDF
- extract the resources from the PDF
- validate these against external individual validators
- combine the validation results
PDFBox can surely do all PDF related tasks. Doing a full validation of the PDF
and all resources against their individual standards is beyond scope of the
PDFBox project and not needed for PDF/A validation.
> create ValidationWarnings
> -------------------------
>
> Key: PDFBOX-2562
> URL: https://issues.apache.org/jira/browse/PDFBOX-2562
> Project: PDFBox
> Issue Type: Sub-task
> Components: Preflight
> Affects Versions: 2.0.0
> Reporter: Ralf Hauser
> Priority: Minor
> Fix For: 2.1.0
>
>
> as seen in the parent Issue PDFBOX-2513 , pdf/A1 is not required to validate
> other standards like TIFF completely.
> On the other hand, the information from the CCITTFaxDecoder is valuable and
> shouldn't be simply discarded.
> Therefore, I suggest that this information is displayed without setting the
> validation result to false.
> ValidationWarnings could have the same logical structure as ValidationError .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
