[
https://issues.apache.org/jira/browse/PDFBOX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238298#comment-17238298
]
Cody Wayne Holmes commented on PDFBOX-5026:
-------------------------------------------
I would say that this certainly isn't a valid PDF. The PDF I have attached was
originally from the PDF.js issue, and I was mostly just trying to keep some
consistency with that implementation. This PDF is also viewable in Adobe,
although Adobe really just 'fixes' the PDF and then views it.
Here is the original issue, but from the metadata I can say that the edits seem
to have been done via Aspose.PDF.
https://github.com/mozilla/pdf.js/issues/9418
> Trailer validation fails when Pages cannot be found in the current trailer
> --------------------------------------------------------------------------
>
> Key: PDFBOX-5026
> URL: https://issues.apache.org/jira/browse/PDFBOX-5026
> Project: PDFBox
> Issue Type: Bug
> Affects Versions: 2.0.21
> Reporter: Cody Wayne Holmes
> Priority: Major
> Attachments: issue9418.pdf
>
>
> I am seeing an issue where multiple trailers exist for a PDF, but the trailer
> that is being found does not contain a Pages object in the Root.
> The PDF does have a trailer that can be read with Pages in the root but the
> brute force approach needs to be taken when parsing is lenient.
> This issue can be seen as being resolved in pdf.js here
> [https://github.com/mozilla/pdf.js/commit/56e3648b656bed1bf4ff52aa3cd70e8a8e53b56f]
> And sample pdf:
> https://github.com/mozilla/pdf.js/blob/master/test/pdfs/issue9418.pdf
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
