Created an attachment (id=18774)
The LaTeX source file
If I use the T1 fonts in LaTeX, Evince cannot print the PDF files any more. Actually printing takes very long and outputs a rastered image. With the Adobe Reader everything works fine. In the related Ubuntu bug report (https://bugs.launchpad.net/ubuntu/+source/evince/+bug/227186), Sebastian Bacher asked to open a bug report for poppler. Actually I'm not sure, whether this is a bug in poppler or in cairo. There is another related bug report in Launchpad (https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/150187).
Here are the details:
I created a small sample LaTeX file (test.tex), which demonstrates the bug. If I compile it without the "fontenc" package using pdflatex, everything works fine in Evince. I named this PDF file "good.pdf". If I compile it with the "fontenc" package (and the option "T1", which uses fonts of a certain LaTeX font encoding), pdflatex creates a PDF file ("wrong.pdf") that Evince cannot print correctly any more. I also attach the printing output of Evince, when using the PDF printer. I named these file "good.printed.pdf" and "wrong.printed.pdf".
The following graphic illustrates the described setting.
test.tex
pdflatex: / \
good.pdf wrong.pdf
Evince: | |
good.printed.pdf wrong.printed.pdf
Since the problem is somehow related to fonts, I also compile the font information of pdffonts and the Adobe Reader in the following:
pdffonts on good.pdf:
name type emb sub uni object ID
------------------------------------ ----------------- --- --- --- ---------
FYHDIM+CMSSBX10 Type 1 yes yes no 4 0
PTMTFG+CMR10 Type 1 yes yes no 5 0
pdffonts on good.printed.pdf:
name type emb sub uni object ID
------------------------------------ ----------------- --- --- --- ---------
UFQSLH+f-1-0 Type 1C yes yes yes 10 0
ZRSKVS+f-0-0 Type 1C yes yes yes 8 0
pdffonts on wrong.pdf:
name type emb sub uni object ID
------------------------------------ ----------------- --- --- --- ---------
[none] Type 3 yes no no 4 0
[none] Type 3 yes no no 5 0
pdffonts on wrong.printed.pdf:
name type emb sub uni object ID
------------------------------------ ----------------- --- --- --- ---------
Adobe Reader on good.pdf:
CMR10 (Eingebettete Untergruppe) [engl: embedded subgroup]
Typ: Type 1
Kodierung: Mitgeliefert [engl: Coding: shipped/supported]
CMSSBX10 (Eingebettete Untergruppe)
Typ: Type 1
Kodierung: Mitgeliefert
Adobe Reader on good.printed.pdf:
f-0-0 (Eingebettete Untergruppe)
Typ: Type 1
Kodierung: Benutzerdefiniert [engl: Coding: User defined]
f-1-0 (Eingebettete Untergruppe)
Typ: Type 1
Kodierung: Benutzerdefiniert
Adobe Reader on wrong.pdf:
F16
Typ: Type 3
Kodierung: Benutzerdefiniert
Originalschrift: F16 [engl: source/former/original font: F16]
Originalschrifttyp: Type 3 [engl: original font type: Type 3]
F19
Typ: Type 3
Kodierung: Benutzerdefiniert
Originalschrift: F19
Originalschrifttyp: Type 3
Adobe Reader on wrong.printed.pdf:
(Empty widget)
Evince states version 2.22.2 with poppler 0.6.4 (cairo). It's the Ubuntu 8.04 package. If you need any more information, I'd be glad to help.
Created an attachment (id=18774)
The LaTeX source file
If I use the T1 fonts in LaTeX, Evince cannot print the PDF files any more. Actually printing takes very long and outputs a rastered image. With the Adobe Reader everything works fine. In the related Ubuntu bug report (https:/ /bugs.launchpad .net/ubuntu/ +source/ evince/ +bug/227186), Sebastian Bacher asked to open a bug report for poppler. Actually I'm not sure, whether this is a bug in poppler or in cairo. There is another related bug report in Launchpad (https:/ /bugs.launchpad .net/ubuntu/ +source/ cupsys/ +bug/150187).
Here are the details:
I created a small sample LaTeX file (test.tex), which demonstrates the bug. If I compile it without the "fontenc" package using pdflatex, everything works fine in Evince. I named this PDF file "good.pdf". If I compile it with the "fontenc" package (and the option "T1", which uses fonts of a certain LaTeX font encoding), pdflatex creates a PDF file ("wrong.pdf") that Evince cannot print correctly any more. I also attach the printing output of Evince, when using the PDF printer. I named these file "good.printed.pdf" and "wrong. printed. pdf".
The following graphic illustrates the described setting.
pdflatex: / \
good.pdf wrong.pdf
Evince: | |
good.printed.pdf wrong.printed.pdf
Since the problem is somehow related to fonts, I also compile the font information of pdffonts and the Adobe Reader in the following:
pdffonts on good.pdf: ------- ------- ------- ------- --- ----------------- --- --- --- ---------
name type emb sub uni object ID
-----
FYHDIM+CMSSBX10 Type 1 yes yes no 4 0
PTMTFG+CMR10 Type 1 yes yes no 5 0
pdffonts on good.printed.pdf: ------- ------- ------- ------- --- ----------------- --- --- --- ---------
name type emb sub uni object ID
-----
UFQSLH+f-1-0 Type 1C yes yes yes 10 0
ZRSKVS+f-0-0 Type 1C yes yes yes 8 0
pdffonts on wrong.pdf: ------- ------- ------- ------- --- ----------------- --- --- --- ---------
name type emb sub uni object ID
-----
[none] Type 3 yes no no 4 0
[none] Type 3 yes no no 5 0
pdffonts on wrong.printed.pdf: ------- ------- ------- ------- --- ----------------- --- --- --- ---------
name type emb sub uni object ID
-----
Adobe Reader on good.pdf:
CMR10 (Eingebettete Untergruppe) [engl: embedded subgroup]
Typ: Type 1
Kodierung: Mitgeliefert [engl: Coding: shipped/supported]
CMSSBX10 (Eingebettete Untergruppe)
Typ: Type 1
Kodierung: Mitgeliefert
Adobe Reader on good.printed.pdf:
f-0-0 (Eingebettete Untergruppe)
Typ: Type 1
Kodierung: Benutzerdefiniert [engl: Coding: User defined]
f-1-0 (Eingebettete Untergruppe)
Typ: Type 1
Kodierung: Benutzerdefiniert
Adobe Reader on wrong.pdf: rift: F16 [engl: source/ former/ original font: F16] rifttyp: Type 3 [engl: original font type: Type 3] rift: F19 rifttyp: Type 3
F16
Typ: Type 3
Kodierung: Benutzerdefiniert
Originalsch
Originalsch
F19
Typ: Type 3
Kodierung: Benutzerdefiniert
Originalsch
Originalsch
Adobe Reader on wrong.printed.pdf:
(Empty widget)
Evince states version 2.22.2 with poppler 0.6.4 (cairo). It's the Ubuntu 8.04 package. If you need any more information, I'd be glad to help.
Sincerly, Simon