[
https://issues.apache.org/jira/browse/PDFBOX-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424517#comment-17424517
]
Oliver Schmidtmer commented on PDFBOX-5283:
-------------------------------------------
Ok, in the file from[
https://github.com/mozilla/pdf.js/issues/10326|https://github.com/mozilla/pdf.js/issues/10326]
the entries for 4, 5 and 6 all point to wrong objects.
"found wrong object number. expected [4] found [5]
found wrong object number. expected [5] found [6]
found wrong object number. expected [6] found [4]"
So I changed the {color:#57606a}findObjectKey{color} to return a corrected
Object key, but to only replace the original entry if it was not valid. That
seems to work for both files.
> No Content - xRef / Obj Parsing
> -------------------------------
>
> Key: PDFBOX-5283
> URL: https://issues.apache.org/jira/browse/PDFBOX-5283
> Project: PDFBox
> Issue Type: Bug
> Components: Parsing
> Affects Versions: 2.0.24, 3.0.0 PDFBox
> Reporter: Oliver Schmidtmer
> Priority: Major
> Attachments: Lieferschein_110300.pdf
>
>
> There seems to be an issue with xRef / object reading when parsing the
> attached pdf.
> The PDF itself has for example two objects with the ref "8 0 R":
> One at position 1967 with a "/Content" entry.
> One at position 7782 without a "/Content" entry.
> Both are referenced in the XRef Table, so there seems to be something off.
> Probably Acrobat, etc. are using the first object, while PDFBox is using the
> second one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
