You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Robert Muir (Created) (JIRA)" <ji...@apache.org> on 2011/10/02 22:08:34 UTC

[jira] [Created] (PDFBOX-1127) PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.

PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.
---------------------------------------------------------------

                 Key: PDFBOX-1127
                 URL: https://issues.apache.org/jira/browse/PDFBOX-1127
             Project: PDFBox
          Issue Type: Bug
    Affects Versions: 1.7.0
         Environment: Tested trunk r1177011
            Reporter: Robert Muir


We had a user report this PDF to the lucene lists: http://www.lucidimagination.com/search/document/7a8c14a534d9a84c/tika_can_not_parse_all_of_the_persian_pdf_files

I asked them to create a TIKA issue (TIKA-713) and attach the PDF file

Upon inspection, the fonts used in the PDF have custom encodings (that map the characters to U+0001, U+0002, ...), however they contain a mapping for the font to unicode >>/Type/Encoding/BaseEncoding/WinAnsiEncoding/Differences, but PDFbox doesnt use this mapping. If you use ExtractText it extracts the raw control characters instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (PDFBOX-1127) PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.

Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PDFBOX-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir updated PDFBOX-1127:
--------------------------------

    Attachment: encoding.jpg

Screenshot showing the glyph list in fontforge and the mapping from the PDF file and how they correspond
                
> PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.
> ---------------------------------------------------------------
>
>                 Key: PDFBOX-1127
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1127
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: Tested trunk r1177011
>            Reporter: Robert Muir
>         Attachments: ebrat.pdf, encoding.jpg
>
>
> We had a user report this PDF to the lucene lists: http://www.lucidimagination.com/search/document/7a8c14a534d9a84c/tika_can_not_parse_all_of_the_persian_pdf_files
> I asked them to create a TIKA issue (TIKA-713) and attach the PDF file
> Upon inspection, the fonts used in the PDF have custom encodings (that map the characters to U+0001, U+0002, ...), however they contain a mapping for the font to unicode >>/Type/Encoding/BaseEncoding/WinAnsiEncoding/Differences, but PDFbox doesnt use this mapping. If you use ExtractText it extracts the raw control characters instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (PDFBOX-1127) PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.

Posted by "Andreas Lehmkühler (Resolved JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PDFBOX-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Lehmkühler resolved PDFBOX-1127.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.7.0
         Assignee: Andreas Lehmkühler
    
> PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.
> ---------------------------------------------------------------
>
>                 Key: PDFBOX-1127
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1127
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: Tested trunk r1177011
>            Reporter: Robert Muir
>            Assignee: Andreas Lehmkühler
>             Fix For: 1.7.0
>
>         Attachments: PDFBOX1127-ebrat.txt, ebrat.pdf, encoding.jpg
>
>
> We had a user report this PDF to the lucene lists: http://www.lucidimagination.com/search/document/7a8c14a534d9a84c/tika_can_not_parse_all_of_the_persian_pdf_files
> I asked them to create a TIKA issue (TIKA-713) and attach the PDF file
> Upon inspection, the fonts used in the PDF have custom encodings (that map the characters to U+0001, U+0002, ...), however they contain a mapping for the font to unicode >>/Type/Encoding/BaseEncoding/WinAnsiEncoding/Differences, but PDFbox doesnt use this mapping. If you use ExtractText it extracts the raw control characters instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (PDFBOX-1127) PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.

Posted by "Robert Muir (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PDFBOX-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir updated PDFBOX-1127:
--------------------------------

    Attachment: ebrat.pdf

test file from TIKA-713
                
> PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.
> ---------------------------------------------------------------
>
>                 Key: PDFBOX-1127
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1127
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: Tested trunk r1177011
>            Reporter: Robert Muir
>         Attachments: ebrat.pdf, encoding.jpg
>
>
> We had a user report this PDF to the lucene lists: http://www.lucidimagination.com/search/document/7a8c14a534d9a84c/tika_can_not_parse_all_of_the_persian_pdf_files
> I asked them to create a TIKA issue (TIKA-713) and attach the PDF file
> Upon inspection, the fonts used in the PDF have custom encodings (that map the characters to U+0001, U+0002, ...), however they contain a mapping for the font to unicode >>/Type/Encoding/BaseEncoding/WinAnsiEncoding/Differences, but PDFbox doesnt use this mapping. If you use ExtractText it extracts the raw control characters instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (PDFBOX-1127) PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.

Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PDFBOX-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119370#comment-13119370 ] 

Robert Muir commented on PDFBOX-1127:
-------------------------------------

Thank you!
                
> PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.
> ---------------------------------------------------------------
>
>                 Key: PDFBOX-1127
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1127
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: Tested trunk r1177011
>            Reporter: Robert Muir
>            Assignee: Andreas Lehmkühler
>             Fix For: 1.7.0
>
>         Attachments: PDFBOX1127-ebrat.txt, ebrat.pdf, encoding.jpg
>
>
> We had a user report this PDF to the lucene lists: http://www.lucidimagination.com/search/document/7a8c14a534d9a84c/tika_can_not_parse_all_of_the_persian_pdf_files
> I asked them to create a TIKA issue (TIKA-713) and attach the PDF file
> Upon inspection, the fonts used in the PDF have custom encodings (that map the characters to U+0001, U+0002, ...), however they contain a mapping for the font to unicode >>/Type/Encoding/BaseEncoding/WinAnsiEncoding/Differences, but PDFbox doesnt use this mapping. If you use ExtractText it extracts the raw control characters instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (PDFBOX-1127) PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.

Posted by "Andreas Lehmkühler (Updated JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PDFBOX-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Lehmkühler updated PDFBOX-1127:
---------------------------------------

    Attachment: PDFBOX1127-ebrat.txt

I fixed the issue in revision 1178428. Most of the text is now readable, see the attached result of ExtractText -sort .
                
> PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.
> ---------------------------------------------------------------
>
>                 Key: PDFBOX-1127
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1127
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: Tested trunk r1177011
>            Reporter: Robert Muir
>             Fix For: 1.7.0
>
>         Attachments: PDFBOX1127-ebrat.txt, ebrat.pdf, encoding.jpg
>
>
> We had a user report this PDF to the lucene lists: http://www.lucidimagination.com/search/document/7a8c14a534d9a84c/tika_can_not_parse_all_of_the_persian_pdf_files
> I asked them to create a TIKA issue (TIKA-713) and attach the PDF file
> Upon inspection, the fonts used in the PDF have custom encodings (that map the characters to U+0001, U+0002, ...), however they contain a mapping for the font to unicode >>/Type/Encoding/BaseEncoding/WinAnsiEncoding/Differences, but PDFbox doesnt use this mapping. If you use ExtractText it extracts the raw control characters instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (PDFBOX-1127) PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.

Posted by "Ahmad Ajiloo (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PDFBOX-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ahmad Ajiloo updated PDFBOX-1127:
---------------------------------

    Comment: was deleted

(was: I'm testing new Encoding.java file with other persian pdf files. )
    
> PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.
> ---------------------------------------------------------------
>
>                 Key: PDFBOX-1127
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1127
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: Tested trunk r1177011
>            Reporter: Robert Muir
>            Assignee: Andreas Lehmkühler
>             Fix For: 1.7.0
>
>         Attachments: PDFBOX1127-ebrat.txt, ebrat.pdf, encoding.jpg
>
>
> We had a user report this PDF to the lucene lists: http://www.lucidimagination.com/search/document/7a8c14a534d9a84c/tika_can_not_parse_all_of_the_persian_pdf_files
> I asked them to create a TIKA issue (TIKA-713) and attach the PDF file
> Upon inspection, the fonts used in the PDF have custom encodings (that map the characters to U+0001, U+0002, ...), however they contain a mapping for the font to unicode >>/Type/Encoding/BaseEncoding/WinAnsiEncoding/Differences, but PDFbox doesnt use this mapping. If you use ExtractText it extracts the raw control characters instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (PDFBOX-1127) PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.

Posted by "Ahmad Ajiloo (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PDFBOX-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140129#comment-13140129 ] 

Ahmad Ajiloo commented on PDFBOX-1127:
--------------------------------------

I'm testing new Encoding.java file with other persian pdf files. 
                
> PDF supplies glyph->unicode mapping, but PDFBox doesn't use it.
> ---------------------------------------------------------------
>
>                 Key: PDFBOX-1127
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1127
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: Tested trunk r1177011
>            Reporter: Robert Muir
>            Assignee: Andreas Lehmkühler
>             Fix For: 1.7.0
>
>         Attachments: PDFBOX1127-ebrat.txt, ebrat.pdf, encoding.jpg
>
>
> We had a user report this PDF to the lucene lists: http://www.lucidimagination.com/search/document/7a8c14a534d9a84c/tika_can_not_parse_all_of_the_persian_pdf_files
> I asked them to create a TIKA issue (TIKA-713) and attach the PDF file
> Upon inspection, the fonts used in the PDF have custom encodings (that map the characters to U+0001, U+0002, ...), however they contain a mapping for the font to unicode >>/Type/Encoding/BaseEncoding/WinAnsiEncoding/Differences, but PDFbox doesnt use this mapping. If you use ExtractText it extracts the raw control characters instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira