[
https://issues.apache.org/jira/browse/PDFBOX-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679757#comment-14679757
]
Petras commented on PDFBOX-2921:
--------------------------------
Oh, I see. I thought the design of these "processes" and their inclusion
mechanism in {{PreflightConfiguration}} meant them being kind of validation
features, which could be turned off to disable some validations. As neither
{{ValidationProcess}} interface, nor its implementations' JavaDocs do not
indicate such dependency, I made this assumption by reading
{{PreflightConfiguration}} sources. Your post says I was wrong. Then It would
be helpful if somewhere (in {{PreflightConfiguration}} or
{{ValidationProcess}} implementations) indicate on which processes the whole
validation procedure depends and cannot be excluded.
> Validation fails if FontValidationProcess is not used
> -----------------------------------------------------
>
> Key: PDFBOX-2921
> URL: https://issues.apache.org/jira/browse/PDFBOX-2921
> Project: PDFBox
> Issue Type: Bug
> Components: Preflight
> Affects Versions: 1.8.10
> Reporter: Petras
>
> The list validation processes to be used during validation may be controlled
> by removing some of it or providing own implementation in
> {{PreflightConfiguration}}. Unfortunately, there exists some coupling among
> them - if {{FontValidationProcess}} is removed from the processes list,
> {{ContentStreamWrapper}} fails with {{ERROR_FONTS_UNKNOWN_FONT_REF}} error:
> {quote}
> Glyph error, MyriadPro-Regular is unknown wasn't found by the
> FontHelperValdiator
> {quote}
> as it does not get {{FontContainer}} instance for given {{PDFont}} from the
> {{PreflightContext}}. It appears that {{FontValidator}} adds them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
