[Poppler-bugs] [Bug 21395] Points on graphs represented as 'q' not points

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=21395





--- Comment #6 from James Cloos <cloos at jhcloos.com>  2009-04-24 23:21:46 PST ---
That typically happens when the document uses the Zapf Dingbats font
without embedding it, and references it with a name that your local
fontconfig cannot dereference.

I added this to my ~/.fonts.conf some time back to get around this:

<!-- many PDFs use ZapfDingbats rather than Zapf Dingbats -->
 <alias binding="same">
   <family>ZapfDingbats</family>
   <accept><family>Dingbats</family></accept>
 </alias>

As you might guess from the above, one of the issues is that although
fontconfig ignores spaces in font patterns when matching installed
fonts, it does not do so when matching font aliases.  Another issue
is that fontconfig does not cache or match on the fonts’ PostScript
names.

The real Zapf Dingbats font shows up as »ITC Zapf Dingbats« and the
version from GhostScript as »Dingbats«.  Fontconfig’ configuration
file 30-urw-aliases.conf includes this bit:

 <alias binding="same">
   <family>Zapf Dingbats</family>
   <accept><family>Dingbats</family></accept>
 </alias>

but that is not sufficient.

The fontconfig repo at:

 git://people.freedesktop.org/~behdad/fontconfig

includes (IIRC) a patch to ignore spaces when matching aliases.  That,
combined with the code in 30-urw-aliases.conf, should fix your bug.

Until that gets pulled into the upstream repo and/or otherwise
incorporated into the version your distribution ships, adding the
first <alias> block I quoted above to your ~/.fonts.conf should
make this pdf work.

(This bug is most likely a dup.)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.