[
https://issues.apache.org/jira/browse/PDFBOX-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934117#comment-15934117
]
Tilman Hausherr commented on PDFBOX-3725:
-----------------------------------------
Yes one version of veraPDF uses a modified version of PDFBox. Another one
(which I haven't tested) uses their own parser.
However being able to view a file in Adobe doesn't mean it is PDF/A compliant.
Even the blue bar (which you don't have) doesn't mean it is PDF/A compliant.
You need a validator. The one I used yesterday (from PDF-Tools) has existed for
a long time, and we've used it as "gold standard" to improve our own validator
(PDFBox preflight).
In other words: even if we'd somehow be able to parse your alleged type 1 font,
this wouldn't make your file PDF/A compliant. You'd may have to convince every
validator manufacturer that their validator is incorrect.
> Problem with Type1 font parser
> ------------------------------
>
> Key: PDFBOX-3725
> URL: https://issues.apache.org/jira/browse/PDFBOX-3725
> Project: PDFBox
> Issue Type: Bug
> Components: FontBox
> Affects Versions: 2.0.5
> Environment: linux
> Reporter: Wolfgang Hamann
> Priority: Minor
> Attachments: ft70.ps, kcap.pdf
>
>
> the parser uses "readSimpleDict" to parse the Metrics.
> This allows
> /Metrics 100 dict dup begin ....... end def
> but not
> /Metrics 100 dict def Metrics begin ..... end
> This variant seems to work in most other pdf tools, however
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
