Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 1.6.0, 1.8.4, 1.8.5
    • None
    • Rendering
    • None
    • MacOS 10.6, Windows 7, Ubuntu 10.10

    Description

      TestRender.pdf adds an odd-looking (different font?)
      question mark to the end of every line. These are not present in
      the original PDF file. Tested On:

      • Mac OS 10.6
      • Windows 7
      • Ubuntu 10.10

      Attachments

        1. TestRender.pdf
          41 kB
          Sarah Kelley
        2. sakelley_pdf_rendering_problem.zip
          741 kB
          Sarah Kelley

        Issue Links

        Activity

          sakelley Sarah Kelley added a comment -

          This file shows odd looking question marks at the end of every line when rendered as an image.

          sakelley Sarah Kelley added a comment - This file shows odd looking question marks at the end of every line when rendered as an image.
          sakelley Sarah Kelley added a comment -

          Code to demonstrate the problem is in the zip file. See readme.txt.

          sakelley Sarah Kelley added a comment - Code to demonstrate the problem is in the zip file. See readme.txt.

          I get an exclamation mark at the end of each line (displaying the "TestRender.pdf" file with the PDFReader app) with the 1.8 branch, but not with the trunk (which has improved font rendering).

          tilman Tilman Hausherr added a comment - I get an exclamation mark at the end of each line (displaying the "TestRender.pdf" file with the PDFReader app) with the 1.8 branch, but not with the trunk (which has improved font rendering).

          Example of a sequence in that PDF:

          /F3.0 1 Tf 
          (import javax.imageio.metadata.*;) Tj 
          /F3.1 1 Tf 
          (!) Tj 
          ET 
          

          Tf = select font
          TJ = show text
          ET = end text object

          So the "/F3.1" font has this exclamation mark. This is an embedded font that has only one glyph: 33, which is just that. According to my own 2.0 version, code 33 has a null path. In 1.8 it is tried to read the embedded font with awt; createFont() fails with a "FontFormatException: Font name not found", and plan B is to use an awt font, which shows us the "!".

          In other words:

          • 1.8 awt sometimes can't handle fonts correctly
          • this is solved in 2.0 since PDFBOX-490 => duplicate
          • the file really has a "!", try copy & paste in Acrobat Reader
          tilman Tilman Hausherr added a comment - Example of a sequence in that PDF: /F3.0 1 Tf ( import javax.imageio.metadata.*;) Tj /F3.1 1 Tf (!) Tj ET Tf = select font TJ = show text ET = end text object So the "/F3.1" font has this exclamation mark. This is an embedded font that has only one glyph: 33, which is just that. According to my own 2.0 version, code 33 has a null path. In 1.8 it is tried to read the embedded font with awt; createFont() fails with a "FontFormatException: Font name not found", and plan B is to use an awt font, which shows us the "!". In other words: 1.8 awt sometimes can't handle fonts correctly this is solved in 2.0 since PDFBOX-490 => duplicate the file really has a "!", try copy & paste in Acrobat Reader

          People

            Unassigned Unassigned
            sakelley Sarah Kelley
            Votes:
            0 Vote for this issue
            Watchers:
            Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack