ICEpdf
  1. ICEpdf
  2. PDF-664

Rendering issues

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 5.0.3, 5.0.4
          • Fix Version/s: 5.0.4
          • Component/s: Core/Parsing
          • Labels:
            None
          • Environment:
            All
          • Salesforce Case Reference:

            Description

            With the provided PDF it was throwing an ArrayIndexOutOfBoundsException that was reported in PDF-649. Upon testing with the latest build, the error is no longer seen but the rendering of the text is incorrect. The block of text is now rendered to the right and the end of the text is displayed off of the page. It is also inverting the text under the block of text.

              Activity

              Descending order - Click to sort in ascending order
              Patrick Corless made changes -
              Status Resolved [ 5 ] Closed [ 6 ]
              Patrick Corless made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Fix Version/s 5.0.4 [ 11072 ]
              Resolution Fixed [ 1 ]
              Hide
              Permalink
              Patrick Corless added a comment -

              Updated the lexer to correct check length after the byte[] position is incremented. Fix has been checked in on the trunk and 5.0.1 branch.

              Show
              Patrick Corless added a comment - Updated the lexer to correct check length after the byte[] position is incremented. Fix has been checked in on the trunk and 5.0.1 branch.
              Hide
              Permalink
              Patrick Corless added a comment -

              This is a regression in our content parser. The content in question is split over two content stream. In particular the array [...] TJ is split and the array code in our lexer is choking because it's not check the overall stream length when looking for the ending ']'.

              Show
              Patrick Corless added a comment - This is a regression in our content parser. The content in question is split over two content stream. In particular the array [...] TJ is split and the array code in our lexer is choking because it's not check the overall stream length when looking for the ending ']'.
              Arran Mccullough made changes -
              Field Original Value New Value
              Salesforce Case Reference 5007000000W5xKWAAZ
              Arran Mccullough created issue -

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: