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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.7.0
• Environment: Tested trunk r1177011
• Assignee: Andreas Lehmkühler
• Reporter: Robert Muir
• Created: 02/Oct/11 20:08
• Updated: 02/May/13 02:29
• Resolved: 03/Oct/11 15:23

Description

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.

Issue Links

• is depended upon by: TIKA-713 Tika can not parse all of the persian pdf files