Bug 690615

Summary:	no encoding loaded for encoding-less embedded fonts
Product:	MuPDF	Reporter:	zeniko
Component:	mupdf	Assignee:	Tor Andersson <tor.andersson>
Status:	RESOLVED WONTFIX
Severity:	normal
Priority:	P4
Version:	unspecified
Hardware:	All
OS:	All
URL:	http://code.google.com/p/sumatrapdf/issues/detail?id=130
Customer:		Word Size:	---

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.