GNOME Bugzilla – Bug 164754
CID font problem with freetype 2.1.8-2.1.9
Last modified: 2005-01-26 15:32:47 UTC
This two PDF documents do not render properly : http://matias.ca/tactilepro/resources/TactilePro_Infosheet.pdf http://www.davidco.com/pdfs/gtd_workflow_advanced.pdf Letters and graphs are missing. The render in evince look kinda the same for both, so I figured it could be the same bug happening.
Does they work in gpdf?
Created attachment 36329 [details] testfile tactilepro.pdf opened in gpdf (2.8.1) and evince (cvs head) Window on the left is gpdf, on the right is evince. It seems evince does a better job rendering a image(?) in the PDF.
On both test cases evince does a better job at the rendering than gpdf on my PC.
Created attachment 36339 [details] screenshot of evince showing the infosheet pdf Well your evince works better than mine :) Here is a screenshot showing how the tactilepro.pdf file shows up on my computer. Notice how the text is all garbled - you cannot tell what it is about. Marco : the same thing happens to me using gpdf. xpdf and xpdf/cairo just exit, while xpdf-3 shows no text at all, only the images. acroread (v. 5.05 or something) has no problem.
Very strange. My evince and gpdf behave as in Hein-Jan's screenshot. Is there anything special about your freetype2 installation? Which version is it? Did it change recently? What's the difference between xpdf and xpdf-3?
Martin : I plead guilty, I was using a devel version of freetype (pkgconfig shows 9.8.3). I downgraded to freetype 2.1.9 (pkgconfig showing 9.7.3), but it looks the same. No change. Should I downgrade more ? ;-) The difference between xpdf and xpdf-3 is mainly the version number :) I noticed that the two versions sometimes render pdfs differently.
I'm afraid that my evince and gpdf (lastest stable versions both) behave as Vincent shows. Both files contain CID fonts (which I thought I read they were not displayed by gpdf). I don't know what you guys (Martin and Hein-Jan) are doing, but I would like to know how to get it on my computer ;-). BTW xpdf display the same font and character mess that evince and gpdf show.
Vincent: I discovered that Ubuntu is still at 2.1.7. I will try 2.1.9 and see if that breaks evince for me. Pablo: what about your freetype version? I'm asking these freetype questions because you reported that all of xpdf, evince, and gpdf have this problem. It may be totally unrelated to freetype, but I don't know what else might be causing this.
Martin, I use FreeType 2.1.9, but I have just discovered that ggv opens both documents right.
Pablo : ggv is not working for me neither :(
Bug 165166 looks very similar.
*** Bug 165166 has been marked as a duplicate of this bug. ***
*** Bug 164767 has been marked as a duplicate of this bug. ***
After updating freetype from 2.1.7 to 2.1.9 I can reproduce this problem. Pablo: ggv doesn't use freetype.
This freetype patch might help. http://thread.gmane.org/gmane.comp.fonts.freetype.devel/2199 I can't test now. If it works, this would be NOTGNOME. Any objections?
The objection being, it does not work (unless I've borked my patching)
It doesn't work for Marco either (and I found a mail that says that the patch is indeed not the solution for this problem). Sorry.
Fixed in cvs
This totally rocks. Thank you !