Summary: | No text displayed in PDF | ||
---|---|---|---|
Product: | poppler | Reporter: | Jonathan Riddell <jr> |
Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | stuart.jarvis |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | this is a description |
Description
Jonathan Riddell
2009-01-20 02:11:16 UTC
Created attachment 22110 [details]
this is a description
The text in this PDF does not display on the second page.
Viewed in Okular with poppler 0.8.7-1ubuntu1 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/) 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. 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. Which freetype version? 2.3.7 is known to have several problems, can you try either with 2.3.8? 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 Yep, fixed with freetype 2.3.8, I had 2.3.7 before - thanks for looking in to this. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.