Bug 692606 - prefer BaseFont over FontName (more often)
Summary: prefer BaseFont over FontName (more often)
Status: RESOLVED FIXED
Alias: None
Product: MuPDF
Classification: Unclassified
Component: mupdf (show other bugs)
Version: unspecified
Hardware: PC Windows 7
: P4 normal
Assignee: MuPDF bugs
URL: http://code.google.com/p/sumatrapdf/i...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-17 05:58 UTC by zeniko
Modified: 2014-04-17 05:48 UTC (History)
1 user (show)

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-10-17 05:58:35 UTC 
The document at the URL has a BaseFont /Georgia and a FontDescriptor with FontName /Courier and for another font it's /Georgia,Bold and /Courier . MuPDF inconsistently uses /Courier in the first case and /Georgia,Bold in the second, whereas the expected behavior is to use both Georgia variants (which is also what Adobe Reader does).
Comment 1 Tor Andersson 2012-07-20 15:01:37 UTC 
The linked file is 404'd.

Are there any cases where using the FontName rather than the
BaseName is actually preferred? I've tried ignoring the FontName
altogether and get one progression on the test files and no
regressions. Maybe that will end up being an easier approach?
Comment 2 zeniko 2012-07-21 20:22:15 UTC 
(In reply to comment #1)
> Are there any cases where using the FontName rather than the
> BaseName is actually preferred?

http://bugs.ghostscript.com/show_bug.cgi?id=691570#c4

(also note that in that case, cutting the name part before the '+' does the wrong thing - which is why we only check the 7th character and not the entire name for a '+')