Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.1
    • Fix Version/s: 1.7.0
    • Component/s: Utilities
    • Labels:
      None
    • Environment:
      JDK 1.6.0_22

      Description

      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?

        Activity

        Hide
        MH added a comment - - edited

        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.

        Show
        MH added a comment - - edited 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.
        Hide
        Andreas Lehmkühler added a comment -

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

        Thanks for the report!

        Show
        Andreas Lehmkühler added a comment - I fixed this in revision 1224791. The PDFMergerUtility now uses the highest version of all pdfs for the destination document. Thanks for the report!

          People

          • Assignee:
            Andreas Lehmkühler
            Reporter:
            MH
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development