Created attachment 15926 [details]
an example of a wrongly displayed pdf file ( generated with pdflatex )

For this file to display correctly, changes to libgnomeprint are
needed, see http://bugzilla.gnome.org/show_bug.cgi?id=109585. I'm
waiting for comments from the gnome-print maintainer.

i am seeing the same thing here (dont know if my PDF's have fonts
embedded though). works under gv/gs etc

btw.. much nice than ggv!!! :-D any plans to implement the gs library
for PS files as well??

to find out if it uses embedded fonts: use pdffonts from Xpdf on the
file. Any font except Courier (New), Helvetica/Arial, Times (New
Roman), Symbol and Zapf Dingbats has to be embedded for consistent
display across computers. The ``emb'' column in pdffonts' output says
if the font is embedded in the file.

using the gs library (I hope I understand you correctly) gpdf won't
use ghostscript in the near future, if at all. But maybe you want to
try an experimental ggv branch 

cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org/cvs/gnome co -r
GTK_GS_REWRITE_4_LIBGS ggv

I think Jaka has ported ggv to use libgs in that branch. I don't know
if it works, though (haven't tried).

*** Bug 115378 has been marked as a duplicate of this bug. ***

i tried this on the 0.104 release, and i am still not getting math
fonts  :-( (Changelog said there was some support now, so i thought
i'd check it out). in fact... configure isnt even checking to see if i
have t1lib installed... im sure that has something to do with it.
configure.in has all the t1lib stuff commented out??

i know this should maybe go in a mailing list question, but, does gpdf
even utilise t1lib??

Uh. That news entry was too early. It works only with gnome-print from
cvs. I should have explained that. Sorry for the confusion.

The commented out t1lib checks are no problem. The gnome renderer of
xpdf uses gnome-print to access fonts (which uses freetype2 which
understands type 1).

And there's no gpdf mailing list...

is that gnomeprint from the gnoem2.3 CVS branch, or the 2.2 branch?
i'd really like to try out a patch on libgnomeprint-2.2.1.3 to see
this working.

You can use either HEAD or the gnome-2-2 branch

Sorry for the spam. If it wasn't obvious: you have to recompile gpdf
with that new gnome-print because the configure script checks if
gnome-print has the necessary features.

The cvs changes of July are available in stable gnome-print 2.4.
Current gpdf renders this document the same way as xpdf.

Just make sure that gpdf's configure said:

checking whether gnome-print has sane private headers... yes