Bug 692289 - generate proper names for symbolic Type 1 glyphs without explicit encoding
Summary: generate proper names for symbolic Type 1 glyphs without explicit encoding
Status: RESOLVED FIXED
Alias: None
Product: MuPDF
Classification: Unclassified
Component: mupdf (show other bugs)
Version: unspecified
Hardware: PC Windows 7
: P4 normal
Assignee: Tor Andersson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-19 17:33 UTC by zeniko
Modified: 2012-07-24 09:18 UTC (History)
0 users

See Also:
Customer:
Word Size: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description zeniko 2011-06-19 17:33:37 UTC 
See e.g. http://www.ijee.ie/articles/Vol17-4and5/IJEE1245.pdf for a document without an explicit encoding for the embedded Type 1 fonts and non-standard glyph names (/C32, /C65, etc.) for no ToUnicode mapping can be generated.

Adobe Reader seems to just use the glyph's index as its Unicode code point. For the linked document, using the glyph index as PdfDocEncoding code point would however yield better results.

Our preliminary fix: http://code.google.com/p/sumatrapdf/source/detail?r=3930
Comment 1 Tor Andersson 2012-07-24 09:18:57 UTC 
commit 93afe454084a1affa050b3ae71674dcfc0ce6a20
Author: Tor Andersson <tor.andersson@artifex.com>
Date:   Mon Jul 23 13:12:43 2012 +0200

    Fallback case for type 1 fonts without encoding and non-standard glyph names.
    
    Fixes bug #692289