ICEpdf
  1. ICEpdf
  2. PDF-1166

Missing text content on first page of document

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 6.2.4
          • Fix Version/s: 6.2.5
          • Component/s: Core/Rendering
          • Labels:
            None
          • Environment:
            PRO

            Description

            PDF in question has no text visible or not rendered on first page. Text is displayed on all other pages. The OS version render the first page correctly but using a less then perfect font. Further analysis is needed but suspect this might be a parsing issue.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Patrick Corless added a comment -

              Interesting corner case here. The first page is make up of 8 content streams. The first content stream ends with:

              -0.0102 Tc -0.0218 Tw 27.0001 0 0 27.0001 54.0001 724.2301 Tm
              [

              Where the last byte is the '[' or start array token. The next stream contains the rest of the array declaration:

              (T)118(r)18(aditional IRA C)9(ustodial Ac)9(c)9(ount Agr)18(eement)]TJ ...

              We have code in the Lexer to move to the next content stream when the end is reach but had an old corner case where if the '[' was the last token we'd just return an empty array. If memory serves me correctly this was for a malformed content stream that didn't have an end array ']'. I've made a small change to the lexer to take into consideration both cases and the PDF renders correctly.

              Will need a full QA test as this is a fairly high risk change.

              Show
              Patrick Corless added a comment - Interesting corner case here. The first page is make up of 8 content streams. The first content stream ends with: -0.0102 Tc -0.0218 Tw 27.0001 0 0 27.0001 54.0001 724.2301 Tm [ Where the last byte is the '[' or start array token. The next stream contains the rest of the array declaration: (T)118(r)18(aditional IRA C)9(ustodial Ac)9(c)9(ount Agr)18(eement)]TJ ... We have code in the Lexer to move to the next content stream when the end is reach but had an old corner case where if the ' [' was the last token we'd just return an empty array. If memory serves me correctly this was for a malformed content stream that didn't have an end array '] '. I've made a small change to the lexer to take into consideration both cases and the PDF renders correctly. Will need a full QA test as this is a fairly high risk change.
              Hide
              Permalink
              Patrick Corless added a comment -

              Marking as fixed.

              Show
              Patrick Corless added a comment - Marking as fixed.

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: