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

Stefan Ziegler commented on PDFBOX-5429:
----------------------------------------

Hi, I've attached a sample pdf file which I have stripped tp remove sensitive 
data. When you try to merge this PDF with another one, then you will get an 
error like {*}Loop within object COSObject\{101, 0}{*}. This worked with prior 
versions of pdfbox, but the checkForRecursion  function breaks this support.

This test pdf was provided to us and was created by another tool. This PDF can 
be read by any reader. Maybe the PDF is not built correctly, but with the 
current version of PDFbox you can not process this PDF, which is the worst 
condition. Then better remove checkForRecursion so that you can process it.

The problem here, in my opinion, is not the PDFs created with PDFBox, but the 
PDFs created by the many other programs that do not always have the best PDF 
export.

> PDFCloneUtility.checkForRecursion breaks support for some existing PDFs
> -----------------------------------------------------------------------
>
>                 Key: PDFBOX-5429
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-5429
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 2.0.26
>            Reporter: Stefan Ziegler
>            Priority: Minor
>         Attachments: testpdf_stripped.pdf
>
>
> This new PDFCloneUtility.checkForRecursion function breaks support for a lot 
> of existing PDFs. I've seen a lot of documents where the /Prev and /Next 
> entries point to the parent element. So this breaks support for a lot of 
> existing PDFs which could be processed before. I would suggest to remove 
> these new check.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to