ICEpdf
  1. ICEpdf
  2. PDF-313

Investigate toUnicode copy error.

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 6.0
    • Fix Version/s: None
    • Component/s: Core/Parsing
    • Labels:
      None
    • Environment:
      any

      Description

      A user has reported a copy text cmap error. The document is quite complex and unfortuantely a CID with numerous toUnicode cmaps which makes tracking down the potential error very difficult.

      when "HONG KONG" is selected in the first paragraph of "People fleeing disasters..." the resulting text is "HoNG KoNG". Once the section of the content stream responsible for the output can be isolated I can check with the corresponding cmap if the there is a bug in ICEpdf or if we're doing the correct mapping.

      I suspect a bug as acrobat return "HONG KONG".
      1. exp.pdf
        240 kB
        Patrick Corless

        Activity

        Patrick Corless created issue -
        Hide
        Patrick Corless added a comment -

        sample pdf.

        Show
        Patrick Corless added a comment - sample pdf.
        Patrick Corless made changes -
        Field Original Value New Value
        Attachment exp.pdf [ 13325 ]
        Hide
        Patrick Corless added a comment -

        Pushing to 4.3.

        Show
        Patrick Corless added a comment - Pushing to 4.3.
        Patrick Corless made changes -
        Salesforce Case []
        Fix Version/s 4.3 [ 10266 ]
        Fix Version/s 4.2.2 [ 10265 ]
        Hide
        Patrick Corless added a comment -

        I was hoping this was going to be fixed as part of some fixes made to cmap parsing for CID fonts but that appears not to be the case. I still need to verify that we are doing something wrong but have run out of time for 4.3, pushing to 5.0.

        Show
        Patrick Corless added a comment - I was hoping this was going to be fixed as part of some fixes made to cmap parsing for CID fonts but that appears not to be the case. I still need to verify that we are doing something wrong but have run out of time for 4.3, pushing to 5.0.
        Patrick Corless made changes -
        Salesforce Case []
        Fix Version/s 5.0 [ 10314 ]
        Fix Version/s 4.3 [ 10266 ]
        Patrick Corless made changes -
        Fix Version/s 5.0.1 [ 10872 ]
        Fix Version/s 5.0 [ 10314 ]
        Patrick Corless made changes -
        Fix Version/s 5.1 [ 10675 ]
        Fix Version/s 5.0.1 [ 10872 ]
        Patrick Corless made changes -
        Affects Version/s 5.2 [ 10970 ]
        Affects Version/s 4.2.1 [ 10272 ]
        Patrick Corless made changes -
        Fix Version/s 5.2 [ 10970 ]
        Fix Version/s 5.1 [ 10675 ]
        Patrick Corless made changes -
        Fix Version/s 5.3 [ 12070 ]
        Fix Version/s 5.2 [ 10970 ]
        Patrick Corless made changes -
        Fix Version/s 6.1 [ 12070 ]

          People

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

            Dates

            • Created:
              Updated: