[ 
https://issues.apache.org/jira/browse/PDFBOX-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231158#comment-14231158
 ] 

Maruan Sahyoun commented on PDFBOX-2533:
----------------------------------------

[~tilman] Disclaimer I didn't look into the code in detail so my comment might 
be invalid.

As a COSArray may not only contain COSString but also other COS type entries 
shouldn’t the block in the decrypt method

{code}
 else if (pb instanceof COSArray)
        {
            final COSArray array = (COSArray) pb;
            for (int aIdx = 0, len = array.size(); aIdx < len; aIdx++)
            {
                if (array.get(aIdx) instanceof COSString)
                {
                    decryptString((COSString) array.get(aIdx), objNr, objGenNr);
                }
            }
        }
{code}

be changed to

{code}
else if (pb instanceof COSArray)
        {
            final COSArray array = (COSArray) pb;
            for (int aIdx = 0, len = array.size(); aIdx < len; aIdx++)
            {
                    decrypt(array.get(aIdx), objNr, objGenNr);
            }
        }
{code}

The same might apply to decryptDictionary()

> 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)

Reply via email to