Created attachment 25120 [details] Correct rendering in acroread When I look at a graph created in Sweave that has been compiled into a pdf in Evince then the points in the graph are represented as 'q' not as points. This always happens. I was directed here from bugs.gnome.org.
Created attachment 25121 [details] Incorrect rendering in Evince
One other thing ... this happens on Fedora 10 and Mandriva 2009.1.
Can you please attach the document itself/give a link on it?
Created attachment 25123 [details] PDF of incorrectly rendered points
I hit the wrong key. This bug is most likely a dup of bug #18002.
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.)
Thanks added that to .fonts.conf did solve my problem. That bug report does look similar http://bugs.freedesktop.org/show_bug.cgi?id=18002
*** This bug has been marked as a duplicate of bug 18002 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.