I've stumbled over various rendering problems with evince before, and mostly
just lived with them.  One such example is the data sheet for the Linear
Technologies LTC1682 charge pump regulator IC, in which the text labels on
the schematic at the bottom of page one render some weird glyph instead of
the expected symbol for 'micro'.  Both xpdf and acroread get it right:

http://www.linear.com/pc/downloadDocument.do?navId=H0,C1,C1003,C1039,C1
133,P1747,D1952

Today, however, I stumbled over a document that evince fails to render in a
much more dramatic and devastating way, that again both xpdf and acroread
handle just fine:

http://www.jst-mfg.com/product/pdf/eng/ePH.pdf

In this datasheet for a JST 2mm connector series, all of the text for
dimensions in the mechanical drawings, and most of the dimensional text in
the tables, fails to render at all.  No visible errors or warnings, the image
is just displayed without the associated text.

On this document, xpdf streams errors like this in the invoking shell window:

	Error: Unknown character collection 'Adobe-Japan1'

However, the resulting rendering is virtually identical to the rendering from
acroread, and completely useable.

Bdale

This document looks fine to me, using evince from experimental and
poppler 0.8.7-1, but I might have overlooked something.

Does this work if you install poppler-data (from non-free?).

I installed the evince from experimental, and see no change.  The glyph
for 'micro' is still rendering wrong... look at the capacitor values,
they should look sort of like 'uF' but the first glyph shows up here as
a sideways sort of squiggle that I don't recognize.

Nope, no change with evince from experimental and poppler-data 0.2.0-2
installed.

Bdale

I'm attaching a screenshot of the lower part of the first page, it looks
okay to me, and the same as what's shown in xpdf here.

If it looks much different on your system, I guess you have some problem
with your fonts.

I tried it myself now, and it seems to work fine. I'm using poppler-data
0.2.1-1 (from experimental), once again, attaching a screenshot.

I'm less sure about this, but you could try and see what fonts are used
on your system for the (non embedded) font families requested in the
first document.

 $ fc-match symbol
 s050000l.pfb: "Standard Symbols L" "Regular"

 $ fc-match zapfdingbats
 DejaVuSans.ttf: "DejaVu Sans" "Book"

 $ fc-match helvetica
 n019003l.pfb: "Nimbus Sans L" "Regular"

For the second document, did you close all the evince windows before
poppler-data was installed? Evince seems to run in a single process.

Are there any errors in the terminal? Without poppler-data, I get a lot
of warnings like this:

 Error: Missing language pack for 'Adobe-Japan1' mapping
 Error: Missing language pack for 'Adobe-Japan1' mapping
 Error: Unknown font tag 'G1'
 Error (109507): No font in show

Just wanted to point to another PDF file where none of the text is rendered:

https://brokernet.kp.org/wps/wcm/connect/1e611480463119a1a439e78045727a81/SB-10_OR_2009.pdf?MOD=AJPERES

Thanks!

I have a document that can be read correctly in Ubuntu 8.10 using Evince
2.22.2 [using popplar 0.6.4] but messes up the rendering in Debian -
same Evince version, but uses popplar 0.8.7.

I can send the document if required.

I have a pdf document in which some (few) lines of text are missing throughout the document. There seems no pattern, some missing on page 4, some missing on page 7, ...
epdfview (0.1.6-7) has the same problem. gv renders the document fully.
I can send screenshots.

Le vendredi 19 mars 2010 à 23:16 +1300, Bruce Ward a écrit :

Can you try with evince 2.28 from unstable?

Cheers,