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 710777 - PDF documents using Charter Type 1 font not printed and previewed correctly
PDF documents using Charter Type 1 font not printed and previewed correctly
Status: RESOLVED NOTGNOME
Product: evince
Classification: Core
Component: printing
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-10-24 08:03 UTC by Holger Arnold
Modified: 2013-11-02 00:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
PDF Test case with Charter Type 1 font (17.90 KB, application/octet-stream)
2013-10-25 05:40 UTC, Germán Poo-Caamaño
Details

Description Holger Arnold 2013-10-24 08:03:38 UTC
Some PDFs embedding the free Charter Type 1 font (http://www.ctan.org/tex-archive/fonts/charter/) are not printed correctly and are not displayed correctly in the print preview opened from Evince.  In particular, the problems are:

Printing:

 1. The dots over German umlauts are missing.
 2. Certain letters (for example, all bold 'M' or all bold 'r' in the document) are replaced by two small dots.
 3. Sometimes, the whole text typeset in the regular Charter font (non-bold, non-italic) is printed in a different font (which looks like Times to my eyes).

Print preview:

 4. German umlauts are not visible.
 5. Sometimes, the previewer simply crashes.

The normal display in Evince is not affected.

All documents I have tested are displayed and printed correctly by xpdf, Ghostscript, Acrobat Reader on Win7, and Apple Preview on OSX.

I have not observed such problems with PDFs using other embedded Type 1 fonts (among others, I tested URW Palladio L and Latin Modern).

The bug seems to be somehow triggered by documents containing accented characters, such as German umlauts.  It's not easy to see, though, what exactly triggers it.  I have created a small test document, which exhibits problems 1. and 4.; it is available at:

    https://drive.google.com/file/d/0BxyCjvRCPNawM2dsUW9kZUQycFE/edit?usp=sharing

Small changes in the documents can make the problems appear or disappear.  For example, in above document, when I delete the quotation marks around the first line of text or add quotation marks around the second line of text, Evince prints the resulting document correctly.  This makes it difficult to create small test documents exhibiting all cited problems (I'm sorry, but I can't share the original documents).

I don't know exactly how printing is done in Evince, but since xpdf and Ghostscript have no problems with these documents, I suspect that this is a bug in Cairo.

Please tell me if I can do more to help you debugging this.

Platform: Linux, x86-64 (Debian testing)

Program/library versions:

  evince: 3.8.3
  cairo: 1.12.16
  poppler: 0.18.4
  ghostscript: 9.05
  cups: 1.6.3
Comment 1 Germán Poo-Caamaño 2013-10-25 05:40:05 UTC
Created attachment 258076 [details]
PDF Test case with Charter Type 1 font
Comment 2 Germán Poo-Caamaño 2013-10-25 05:47:44 UTC
I can reproduce the problem of missing characters with umlauts.  However, the document you uploaded (and that I attached to this bug) does not seem to have any character in bold.  I fail to see them (even in Acroread).

In addition, it is not necessary to test it with a printer. Just printing to a file as PDF and opening the resulting file shows the issue.

Printing to a file as PS and then trying to open it, evince fails. The console shows:

$ evince evince-charter.ps 
undefined -21
undefined -21
undefined -21

(evince:31112): EvinceDocument-CRITICAL **: ev_document_misc_pixbuf_from_surface: assertion `surface' failed
undefined -21
undefined -21
undefined -21
undefined -21
undefined -21
undefined -21
undefined -21

and does not render anything.


However, printing to a PS from Acroread, then opening with Evince (or converting it to PDF with ps2pdf), the printing works as expected. No issue with the umlauts, etc.
Comment 3 Holger Arnold 2013-10-25 07:45:13 UTC
(In reply to comment #2)
> I can reproduce the problem of missing characters with umlauts.  However, the
> document you uploaded (and that I attached to this bug) does not seem to have
> any character in bold.  I fail to see them (even in Acroread).

No, this test document does not contain bold characters.  It's actually not easy to intentionally create a _small_ test document showing all cited problems.  As I wrote in my report, even tiny changes to the text can make the individual problems appear or disappear.  But practically all larger documents typeset using the Charter Type 1 font distributed with Texlive that I tried show the problems.  I will try to create another small test case.
Comment 4 Germán Poo-Caamaño 2013-11-02 00:26:35 UTC
I forwarded the report to Poppler's bugzilla. There you can track the
progress.

https://bugs.freedesktop.org/show_bug.cgi?id=71151