= Transfering this bug from GNOME Bugzilla:
The file at http://www.kniivila.net/deponejo/kongresa.pdf prints an overlay of
the file and of raw code (it seems) on my printer (HP LaserJet 4L). The file
prints properly with xpdf and gpdf. The preview is fine.
Maybe useful comment:
I have very similar, probably the same problem. I did some investigations on the
postscript files generated by xpdf and evince. The problem is that the file from
xpdf contains 'embeded' (I do not know if it is the official name) fonts and the
file from evince not. Actually, one can do diff of two postscript files and
apply _only_ the chunk that contains fonts on evince postscript. The file then
prints OK. This method works also for the originally reported file.
With the attached patch all (two) test files print correctly. However, the
correction is too obvious and maybe I'm missing something. Without the patch
the body of the first loop in PSOutputDev::writeDocSetup is never executed.
Created attachment 3386 [details] [review]
Here is the promissed patch
could somebody comment on the patch? printing of non-ascii chars is broken for
the moment and I would like to get that fixed for Ubuntu 5.10 by example
I reproduced this without any "international" characters in my PDF file, and the
attached patch fixes it.
Created attachment 3489 [details] [review]
Unified diff, with directory information (there are 3 poppler-page.cc files in
The patch looks good to me. We already adjust for the different 0- and 1-based
page number conventions in the poppler_ps_file_new() constructor, so the '+ 1'
in poppler_page_render_to_ps() is wrong and causes the PSOutputDev constructor
to miss ::init for 1-page documents.
Patch applied to 0.4 branch and head.
*** Bug 4598 has been marked as a duplicate of this bug. ***
*** Bug 4577 has been marked as a duplicate of this bug. ***