ICEpdf
  1. ICEpdf
  2. PDF-924

Incorrect font bounds resulting in missing printed content.

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 6.0.0_P01
          • Fix Version/s: 6.1.1
          • Component/s: Core/Parsing, Printing
          • Labels:
            None
          • Environment:
            any

            Description

            The support case in question has a few PDFs that have glyph bounds that are very large or in the incorrect place. This is causing artifact issues with text selection as well as messing up printing as same glyphs are getting clipped by the print band clip.

              Activity

              Ascending order - Click to sort in descending order
              Patrick Corless created issue -
              Patrick Corless made changes -
              Field Original Value New Value
              Fix Version/s 6.1 [ 12070 ]
              Arran Mccullough made changes -
              Support Case References Support Case #13495 - https://icesoft.my.salesforce.com/5007000001Hcdn9
              Patrick Corless made changes -
              Fix Version/s 6.1.1 [ 12975 ]
              Fix Version/s 6.1 [ 12070 ]
              Hide
              Permalink
              Patrick Corless added a comment -

              It would appear the bounds for the type 3 fonts are incorrect. Adobe seems to get the same result as our calculation which can be seen by the text selection highlighting.

              Because we can't control the printers clipping bounds or correct for the font's bounds I've added a new system property that will disable the intersection calculation for type 3 fonts. So the end user can use -Dorg.icepdf.core.text.optimized.type3=false to fix the printing issue.

              Show
              Patrick Corless added a comment - It would appear the bounds for the type 3 fonts are incorrect. Adobe seems to get the same result as our calculation which can be seen by the text selection highlighting. Because we can't control the printers clipping bounds or correct for the font's bounds I've added a new system property that will disable the intersection calculation for type 3 fonts. So the end user can use -Dorg.icepdf.core.text.optimized.type3=false to fix the printing issue.
              Hide
              Permalink
              Patrick Corless added a comment -

              Checked in a fix for trunk and the 6.1 branch.

              Show
              Patrick Corless added a comment - Checked in a fix for trunk and the 6.1 branch.
              Patrick Corless made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #48556 Thu Mar 24 08:34:19 MDT 2016 patrick.corless PDF-924 added new system property org.icepdf.core.text.optimized.type3 which has a default value of true, when set to false the optimized painting will be turned off for type 3 font glyphs.
              Files Changed
              Commit graph MODIFY /icepdf/branches/icepdf-6.1.0/icepdf/core/src/org/icepdf/core/pobjects/graphics/TextSprite.java
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #48557 Thu Mar 24 08:34:29 MDT 2016 patrick.corless PDF-924 added new system property org.icepdf.core.text.optimized.type3 which has a default value of true, when set to false the optimized painting will be turned off for type 3 font glyphs.
              Files Changed
              Commit graph MODIFY /icepdf/trunk/icepdf/core/src/org/icepdf/core/pobjects/graphics/TextSprite.java
              Patrick Corless made changes -
              Status Resolved [ 5 ] Closed [ 6 ]

                People

                • Assignee:
                  Patrick Corless
                  Reporter:
                  Patrick Corless
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: