Bug 19660 - No text displayed in PDF
No text displayed in PDF
Product: poppler
Classification: Unclassified
Component: general
Other All
: medium normal
Assigned To: poppler-bugs
Depends on:
  Show dependency treegraph
Reported: 2009-01-20 02:11 UTC by Jonathan Riddell
Modified: 2009-01-21 11:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

this is a description (718.82 KB, application/pdf)
2009-01-20 02:12 UTC, Jonathan Riddell

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Riddell 2009-01-20 02:11:16 UTC
The text on the second page of this PDF is not displayed
Comment 1 Jonathan Riddell 2009-01-20 02:12:49 UTC
Created attachment 22110 [details]
this is a description

The text in this PDF does not display on the second page.
Comment 2 Jonathan Riddell 2009-01-20 02:19:36 UTC
Viewed in Okular with poppler 0.8.7-1ubuntu1
Comment 3 Stuart Jarvis 2009-01-20 05:42:57 UTC
Same symptoms with poppler 0.87-1.fc10 (Fedora) tested using okular and evince.

There is also text missing on the first page - in top right corner where a few dots are visible. All 'text' that can be seen is in fact graphics I think.

Works ok in Adobe Reader 8 on Windows (tested) and apparently in older poppler versions: (according to http://dot.kde.org/1232445901/1232453792/1232454813/)
Comment 4 Albert Astals Cid 2009-01-20 14:10:44 UTC
Works for me in poppler 0.10.3 if it still fails for you after upgrading to this or a later version please reopen the bug.
Comment 5 Stuart Jarvis 2009-01-21 09:15:36 UTC
Tested with poppler-0.10.3-1.fc11 (from rawhide on fc-10) still the same symptoms.

Running okular with this pdf from konsole I get:

'Error: Illegal entry in bfrange block in ToUnicode CMap'

many times, followed by: 

'okular(3255)/okular (Poppler) PDFGenerator::abstractTextPage: getting text page in generator pdf - rotation: 0 '

once, then back to 'Error: Illegal....'

In case those have any meaning to you.
Comment 6 Albert Astals Cid 2009-01-21 11:19:31 UTC
Which freetype version? 2.3.7 is known to have several problems, can you try either with 2.3.8?
Comment 7 Albert Astals Cid 2009-01-21 11:26:51 UTC
I've just tested with both freetype 2.3.7 and 2.3.8, 2.3.7 fails and 2.3.8 works so i'm closing again. Please reopen if you happen to have 2.3.8
Comment 8 Stuart Jarvis 2009-01-21 11:53:17 UTC
Yep, fixed with freetype 2.3.8, I had 2.3.7 before - thanks for looking in to this.