You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "MH (JIRA)" <ji...@apache.org> on 2010/10/26 17:08:22 UTC

[jira] Created: (PDFBOX-879) PDFMergerUtility

PDFMergerUtility
----------------

                 Key: PDFBOX-879
                 URL: https://issues.apache.org/jira/browse/PDFBOX-879
             Project: PDFBox
          Issue Type: Bug
          Components: Utilities
    Affects Versions: 1.3.1
         Environment: JDK 1.6.0_22
            Reporter: MH


I concatenate PDFs with the PDFMergerUtility. As long as I concat my (with FOP) created PDFs that are in "PDF 1.4" format, I get no issue when viewing the result. But when one of the PDFs is a "PDF 1.2" document, the resulting PDF will also have "PDF 1.2" version. When viewing this concatenated PDF in Acrobat Reader (9), the first (originally PDF-1.2) document gets viewed without errors, but as soon as I scroll further to the second page (with the other PDF-1.4 PDFs), I get errors like

"Fehler auf dieser Seite. Die Seite wird unter Umständen nicht richtig in Acrobat angezeigt. Wenden Sie sich an den Ersteller des PDF-Dokuments, um das Problem zu beheben." (Roughly: errors on this page.)

or

"Ungültiger Parameter." (Roughly: invalid parameter.)

Note: when concatenated with iText 2.1.7, the resulting PDF has version "1.4" and no errors occur in Adobe Reader.

Is it possible to tell the merger to set the PDF Version of the result PDF?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Issue Comment Edited: (PDFBOX-879) PDFMergerUtility

Posted by "MH (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PDFBOX-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925002#action_12925002 ] 

MH edited comment on PDFBOX-879 at 10/26/10 11:52 AM:
------------------------------------------------------

This only happens if the FIRST PDF is version 1.2! When the first PDF has version 1.4 and the second has "1.2", this problem does not occur, i.e. Adobe Reader shows no errors.

Unfortunately, this doesn't happen with all 1.2 documents. I tried to create such a PDF with content that is not "critical". But with my simple documents, it didn't happen. However, even with the simple documents, the effect is visible, that the resulting PDF will get version "1.2" when the 1.2-PDF is the first document.

      was (Author: mhilpert):
    This only happens if the FIRST PDF is version 1.2! When the first PDF has version 1.4 and the second has "1.2", this problem does not occur, i.e. Adobe Reader shows no errors.
  
> PDFMergerUtility
> ----------------
>
>                 Key: PDFBOX-879
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-879
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 1.3.1
>         Environment: JDK 1.6.0_22
>            Reporter: MH
>
> I concatenate PDFs with the PDFMergerUtility. As long as I concat my (with FOP) created PDFs that are in "PDF 1.4" format, I get no issue when viewing the result. But when one of the PDFs is a "PDF 1.2" document, the resulting PDF will also have "PDF 1.2" version. When viewing this concatenated PDF in Acrobat Reader (9), the first (originally PDF-1.2) document gets viewed without errors, but as soon as I scroll further to the second page (with the other PDF-1.4 PDFs), I get errors like
> "Fehler auf dieser Seite. Die Seite wird unter Umständen nicht richtig in Acrobat angezeigt. Wenden Sie sich an den Ersteller des PDF-Dokuments, um das Problem zu beheben." (Roughly: errors on this page.)
> or
> "Ungültiger Parameter." (Roughly: invalid parameter.)
> Note: when concatenated with iText 2.1.7, the resulting PDF has version "1.4" and no errors occur in Adobe Reader.
> Is it possible to tell the merger to set the PDF Version of the result PDF?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] [Resolved] (PDFBOX-879) PDFMergerUtility

Posted by "Andreas Lehmkühler (Resolved JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PDFBOX-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Lehmkühler resolved PDFBOX-879.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.7.0
         Assignee: Andreas Lehmkühler

I fixed this in revision 1224791. The PDFMergerUtility now uses the highest version of all pdfs for the destination document.

Thanks for the report!
                
> PDFMergerUtility
> ----------------
>
>                 Key: PDFBOX-879
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-879
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 1.3.1
>         Environment: JDK 1.6.0_22
>            Reporter: MH
>            Assignee: Andreas Lehmkühler
>             Fix For: 1.7.0
>
>
> I concatenate PDFs with the PDFMergerUtility. As long as I concat my (with FOP) created PDFs that are in "PDF 1.4" format, I get no issue when viewing the result. But when one of the PDFs is a "PDF 1.2" document, the resulting PDF will also have "PDF 1.2" version. When viewing this concatenated PDF in Acrobat Reader (9), the first (originally PDF-1.2) document gets viewed without errors, but as soon as I scroll further to the second page (with the other PDF-1.4 PDFs), I get errors like
> "Fehler auf dieser Seite. Die Seite wird unter Umständen nicht richtig in Acrobat angezeigt. Wenden Sie sich an den Ersteller des PDF-Dokuments, um das Problem zu beheben." (Roughly: errors on this page.)
> or
> "Ungültiger Parameter." (Roughly: invalid parameter.)
> Note: when concatenated with iText 2.1.7, the resulting PDF has version "1.4" and no errors occur in Adobe Reader.
> Is it possible to tell the merger to set the PDF Version of the result PDF?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Commented: (PDFBOX-879) PDFMergerUtility

Posted by "MH (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PDFBOX-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925002#action_12925002 ] 

MH commented on PDFBOX-879:
---------------------------

This only happens if the FIRST PDF is version 1.2! When the first PDF has version 1.4 and the second has "1.2", this problem does not occur, i.e. Adobe Reader shows no errors.

> PDFMergerUtility
> ----------------
>
>                 Key: PDFBOX-879
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-879
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 1.3.1
>         Environment: JDK 1.6.0_22
>            Reporter: MH
>
> I concatenate PDFs with the PDFMergerUtility. As long as I concat my (with FOP) created PDFs that are in "PDF 1.4" format, I get no issue when viewing the result. But when one of the PDFs is a "PDF 1.2" document, the resulting PDF will also have "PDF 1.2" version. When viewing this concatenated PDF in Acrobat Reader (9), the first (originally PDF-1.2) document gets viewed without errors, but as soon as I scroll further to the second page (with the other PDF-1.4 PDFs), I get errors like
> "Fehler auf dieser Seite. Die Seite wird unter Umständen nicht richtig in Acrobat angezeigt. Wenden Sie sich an den Ersteller des PDF-Dokuments, um das Problem zu beheben." (Roughly: errors on this page.)
> or
> "Ungültiger Parameter." (Roughly: invalid parameter.)
> Note: when concatenated with iText 2.1.7, the resulting PDF has version "1.4" and no errors occur in Adobe Reader.
> Is it possible to tell the merger to set the PDF Version of the result PDF?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.