Bug 690615 - no encoding loaded for encoding-less embedded fonts
Summary: no encoding loaded for encoding-less embedded fonts
Status: RESOLVED WONTFIX
Alias: None
Product: MuPDF
Classification: Unclassified
Component: mupdf (show other bugs)
Version: unspecified
Hardware: All All
: P4 normal
Assignee: Tor Andersson
URL: http://code.google.com/p/sumatrapdf/i...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-09 15:22 UTC by zeniko
Modified: 2010-05-20 23:07 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 2009-07-09 15:22:20 UTC 
See the URL for a document which can't be searched when no default encoding is 
loaded for an internal font. Potential patch: http://pastie.org/540652
Comment 1 zeniko 2009-07-30 06:01:11 UTC 
FYI: The potential patch causes documents containing symbolic Type 1 fonts to 
misrender (cf. http://code.google.com/p/sumatrapdf/issues/detail?id=595 ), so the 
following adjustment is needed: http://code.google.com/p/sumatrapdf/source/detail?
r=1333
Comment 2 zeniko 2009-12-11 10:36:29 UTC 
Seems like the restriction mentioned in comment #1 wasn't caused by a symbolic 
Type 1 font but by a CFF font for which FT_Get_Name_Index doesn't yield proper 
results. Patch: http://code.google.com/p/sumatrapdf/source/detail?r=1614
Comment 3 zeniko 2010-01-10 15:09:54 UTC 
See http://code.google.com/p/sumatrapdf/source/detail?r=1674 for a refined patch 
which extracts an embedded encoding for Type 1 fonts, even if it doesn't seem to 
be exposed by FreeType.
Comment 4 Tor Andersson 2010-05-14 23:04:41 UTC 
This is a freetype limitation and should be discussed with the freetype people.