[
https://issues.apache.org/jira/browse/PDFBOX-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102781#comment-13102781
]
William Fausser commented on PDFBOX-1117:
-----------------------------------------
I was thinking that in some cases where it is not a hard error caused by
syntax, that it would be useful to see results of the validation tests. I am
asking because
sometimes there is a need to validate an non PDF/A pdf document. It seems like
all the work is already done and a front end could be developed to just check
the
error returned in order to validate a non-pdf/a. For example, if there is a
need to validate pdfs containing JavaScript, then the error code could be
checked to deny
JavaScript or embedded JavaScript if the current PDF syntax would continue into
the regular validation process.
> [Preflight] Continue the PDF validation after syntax error
> ----------------------------------------------------------
>
> Key: PDFBOX-1117
> URL: https://issues.apache.org/jira/browse/PDFBOX-1117
> Project: PDFBox
> Issue Type: Improvement
> Components: Preflight
> Affects Versions: 1.7.0
> Reporter: Eric Leleu
> Priority: Minor
>
> Currently, the PDF content isn't checked if the PDF Syntax is invalid.
> Study the possibility to continue the validation process if the grammar
> throws an exception.
> It should be possible but I prefer to check that there aren't bad effects.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
