Bug 690634 - Type 3 fonts aren't searchable
Summary: Type 3 fonts aren't searchable
Status: RESOLVED FIXED
Alias: None
Product: MuPDF
Classification: Unclassified
Component: mupdf (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P4 normal
Assignee: Tor Andersson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-16 14:36 UTC by zeniko
Modified: 2009-07-18 05:42 UTC (History)
0 users

See Also:
Customer:
Word Size: ---

Attachments
sample PDF (5.13 KB, application/pdf)
2009-07-16 14:46 UTC, zeniko 		Details
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-16 14:36:17 UTC 
This is due to the fact that FT_Set_Char_Size is called even for Type 3 fonts in 
pdf_unicode.c's extracttext.

Also: Font Differences in the /a65 form aren't recognized (/a65 standing for the 
ASCII 65 character 'A').

See http://code.google.com/p/sumatrapdf/source/detail?r=1311
Comment 1 zeniko 2009-07-16 14:46:22 UTC 
Created attachment 5214 [details]
sample PDF

See http://drop.io/issue_589 for the source.
Comment 2 Tor Andersson 2009-07-18 05:42:08 UTC 
After we added a heuristic to pdf_lookupagl() to also look for "a%d" patterns the Type3 fonts generated by 
TeX & co become searchable.