[
https://issues.apache.org/jira/browse/PDFBOX-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000831#comment-14000831
]
Tilman Hausherr edited comment on PDFBOX-1922 at 5/17/14 6:54 PM:
------------------------------------------------------------------
The non sequential parser didn't have anything to read the header. I simply
copied that part from the "old" parser and then did a seek(0) to restart as if
I hadn't done anything. Now I'm getting the same version numbers for load() and
loadNonSeq() for all my test files. I committed this in rev 1595520 for the
trunk and 1595527 for the 1.8 branch. I will try do a DRY refactoring at a
later time so that this code doesn't exist twice.
Because this is "too good to be true", [~tboehme], [~msahyoun] please have a
look :-)
[[email protected]] Where is the version in the trailer?
was (Author: tilman):
The non sequential parser didn't have anything to read the header. I simply
copied that part from the "old" parser and then did a seek(0) to restart as if
I hadn't done anything. Now I'm getting the same version numbers for load() and
loadNonSeq() for all my test files. I committed this in rev 1595520 for the
trunk. I will try do a DRY refactoring at a later time so that this code
doesn't exist twice.
Because this is "too good to be true", [~tboehme], [~msahyoun] please have a
look :-)
[[email protected]] Where is the version in the trailer?
> NonSequentialParser not reading version in header
> -------------------------------------------------
>
> Key: PDFBOX-1922
> URL: https://issues.apache.org/jira/browse/PDFBOX-1922
> Project: PDFBox
> Issue Type: Bug
> Components: Parsing
> Affects Versions: 1.8.4, 1.8.5, 1.8.6, 2.0.0
> Reporter: Tim Allison
> Priority: Minor
> Attachments: testAnnotations.pdf
>
>
> On older pdf files, the NonSequentialParser returns a different PDFVersion
> than the traditional parser via the call:
> document.getDocument().getVersion().
> I think this is because NonSequentialParser is not reading the header but
> relying on the default 1.4 if no version is found in the trailer.
> Many apologies if this is a duplicate. I feel like I've seen this issue
> elsewhere, but I can't track it down.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
