[
https://issues.apache.org/jira/browse/PDFBOX-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233555#comment-14233555
]
Tilman Hausherr commented on PDFBOX-2533:
-----------------------------------------
Code reviews are always useful, but I believe that the encryption is handled
correctly in the nonsequential parser, because:
- the trailer is parsed before the security handler exists
- same for ID because it is in the trailer
- object streams are done in a branch that doesn't use the security handler
btw it is even more tricky, there are other elements that may not be decrypted,
e.g. the Xref Stream.
About the sequential parser:
- sig is ignored
- object streams to
- don't know about trailer and ID, This depends on whether
document.getDocument().getObjects(); also returns the trailer among the results.
> Poor rendering with non-sequential parser
> -----------------------------------------
>
> Key: PDFBOX-2533
> URL: https://issues.apache.org/jira/browse/PDFBOX-2533
> Project: PDFBox
> Issue Type: Bug
> Components: Parsing
> Affects Versions: 1.8.8, 2.0.0
> Reporter: Tilman Hausherr
> Assignee: Tilman Hausherr
> Fix For: 1.8.8, 2.0.0
>
> Attachments: 905605.pdf
>
>
> p39 + 40 of the attached file are poorly rendered with the non-Sequential
> parser. With the old parser, while the glyphs are not perfect, they represent
> the correct character. This is for 1.8.8.
> In 2.0 the rendering is incorrect, but I didn't test with the old parser
> because that one is no longer available from the command line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
