I have upgraded poppler, poppler-binding and evince to version 0.5.0. opening and pdf file like http://archive.ncsa.uiuc.edu/General/Internet/WWW/HTMLPrimerPDF.pdf I get a big mess instead of text displayed. and evince tells me on the console that it has problems with some fonts: $ evince HTMLPrimerPDF.pdf Error: Couldn't find a font for 'Times Roman' some font thing failed Error: Couldn't find a font for 'Times Bold' some font thing failed Error: Couldn't find a font for 'Times Italic' some font thing failed Error: Couldn't find a font for 'Courier' some font thing failed
This works fine with me for evince. I think this is going to take some work to track down... Lets start with the obvious. Did this work with evince 0.4? Do you have Times and Courier fonts installed? Are you running xfs? If you have Times and Courier, can you select them from the gnome font preferencre? Assuming this all works, we'll get into esoterica afterwards.
(In reply to comment #1) > Lets start with the obvious. Did this work with evince 0.4? Yes. > Do you have Times > and Courier fonts installed? Yes. > Are you running xfs? Shouldn't be relevant, evince uses font-config. But yes. > If you have Times and > Courier, can you select them from the gnome font preferencre? Yes.
Created attachment 77903 [details] emerge-info.txt
That particular error is generated by poppler, not by evince. The font handling in poppler seems fairly straight forward, and is done by font-config. Could you try runing pdftohtml on the file (after verifying that your pdftohtml comes from poppler, of course).
Created attachment 77915 [details] htmlprimerpdf-html.png Here's what the produced HTML looks like -- a bunch of horizontal gray lines on every page. No error messages produced by pdftohtml. donnie@supernova ~ $ pdftohtml HTMLPrimerPDF.pdf Page-1 Page-2 Page-3 Page-4 Page-5 Page-6 Page-7 Page-8 Page-9 Page-10 Page-11 Page-12 Page-13 Page-14 Page-15 Page-16 Page-17 Page-18 Page-19 Page-20 Page-21 Page-22 Page-23 Page-24 donnie@supernova ~ $
Okay, I get the same problem with pdftohtml (I didn't look at my output before), so it's definitely a poppler problem. I'll look into it.
This looks like the upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=5466
Which version of fontconfig do you have? If it's not 2.3.2, could you try 2.3.2? Upgrading to 2.3.2 on my stable box didn't fix the "Couldn't find a font" errors, but it *did* result in actual display of text.
(In reply to comment #8) > Which version of fontconfig do you have? If it's not 2.3.2, could you try > 2.3.2? Upgrading to 2.3.2 on my stable box didn't fix the "Couldn't find a > font" errors, but it *did* result in actual display of text. Not for me -- got 2.3.2, still get garbage text for the Courier font in my test PDF. The posted PDF isn't at that site anymore.
here's another pdf file http://ioc.unesco.org/oceanteacher/oceanteacher2/02_InfTchSciCmm/01_CmpTch/08_MarkUpLangs/01_HTML/BeginnersGuideToHTML.pdf
Created attachment 78224 [details] sample pdf file uploading sample file from http://ioc.unesco.org/oceanteacher/oceanteacher2/02_InfTchSciCmm/01_CmpTch/08_MarkUpLangs/01_HTML/BeginnersGuideToHTML.pdf
Try this temporary workaround: Disable bitmap fonts in your /etc/fonts/local.conf <selectfont> <rejectfont> <pattern> <patelt name="scalable"><bool>false</bool></patelt> </pattern> </rejectfont> </selectfont>
(In reply to comment #12) > Try this temporary workaround: > Disable bitmap fonts in your /etc/fonts/local.conf this works for me.
See also http://bugs.freedesktop.org/show_bug.cgi?id=5758 for a patch.
Created attachment 78394 [details, diff] 5758.bugs.fdo-try-all-fonts.patch
Awesome Ed! This works!!
Fixed in poppler-0.5.0-r2. Thanks.
