After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794315 - Evince dos not render this PDF properly
Evince dos not render this PDF properly
Status: RESOLVED NOTGNOME
Product: evince
Classification: Core
Component: PDF
3.26.x
Other Linux
: Normal major
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-03-14 07:20 UTC by robi
Modified: 2018-03-16 17:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
File where Evince does not show most of the text (106.78 KB, application/pdf)
2018-03-14 07:20 UTC, robi
Details
Screenshot of document rendered by Evince and Acroread side by side (395.82 KB, image/png)
2018-03-14 14:14 UTC, Germán Poo-Caamaño
Details
Screenshot (149.86 KB, image/png)
2018-03-15 07:50 UTC, robi
Details
Another file (39.12 KB, application/pdf)
2018-03-15 09:08 UTC, robi
Details
Screenshot of Foxit Reader rendering the document (231.77 KB, image/png)
2018-03-16 17:26 UTC, Germán Poo-Caamaño
Details

Description robi 2018-03-14 07:20:37 UTC
Created attachment 369645 [details]
File where Evince does not show most of the text

I get a lot PDF files where Evince has trouble rendering them. One of them is the attached one.
Comment 1 Germán Poo-Caamaño 2018-03-14 14:14:52 UTC
Created attachment 369678 [details]
Screenshot of document rendered by Evince and Acroread side by side

May be you more specific about the rendering problem?
What do you see and what do you expect to see? Screenshots of both would be great.

That said, the document has not embedded fonts. That is, it may look different in any computer that does not have the fonts used to produce the document. Even more, Acroread itself says
  "Cannot find or create 'System'. Some characters may not display or
   print correctly."

The PDF reader tries to do the best to render a document. When a font is not found it tries to use a substitute. You can check in the Font section of the Document properties dialog (Alt+P).  Evince also says that it may not render correctly because of the fonts used in the document.

If that is the case, it is not Evince or Poppler (the library used to render PDF) fault.
Comment 2 robi 2018-03-15 07:48:46 UTC
Actually you see it perfectly ok! Attached is an image what I see on three different computers, all of them on ubuntu 16.04 or 17.10. And they all show unreadable mess.
Comment 3 robi 2018-03-15 07:50:08 UTC
Created attachment 369711 [details]
Screenshot

Screenshot of how I see the document
Comment 4 robi 2018-03-15 09:08:23 UTC
Created attachment 369715 [details]
Another file

I finally managed to make comparison of another file received from the same company.
Comment 5 Germán Poo-Caamaño 2018-03-15 14:52:56 UTC
The issue is the same: fonts are not embedded, and it depends on the font configuration in each computer.

To make a PDF than can be read in any device, it must be a PDF/A (PDF for archiving), which embeds the fonts.

That said, in my machine TimesNewRoman is substituted by TexGyreTermes-Regular instead of "Times New Roman", which is different of what fontconfig shows me (fc-match shows correctly "Times New Roman". For example, the text
"PREDLOGI SKLEPOV ZA PONOVLJENI ZBOR LASTNIKOV STAVBE RAKUŠEVA" looks bad because of the font chosen.

Acroread does a better job, although there are some artifacts. Foxit does a much better job.

Anyhow, please file a bug in Poppler, the library used by Evince to render PDF documents:

https://bugs.freedesktop.org/enter_bug.cgi?product=poppler

Perphas Poppler developers might know better why and if there anything that can be done.
Comment 6 robi 2018-03-16 06:31:47 UTC
Thanks for clarification. By the way, Foxit chokes on the second file too.
Comment 7 Germán Poo-Caamaño 2018-03-16 17:26:33 UTC
Created attachment 369793 [details]
Screenshot of Foxit Reader rendering the document

Again, it depends on the fonts you have installed locally. You may want to try installing msttfcorefonts (or whatever the name is for the MS TTF fonts in your distro).

The key issue is that Poppler is not using 'Times New Roman' as a substitute for 'TimesNewRoman' (fontconfig does it, but not Poppler. Maybe I am talking nonsense for a Poppler developer :-). Foxit does it in my computer.