Bug 274055 - Page numbers shown wrong (garbage chars) in the "contents" area of a PDF TOC
Summary: Page numbers shown wrong (garbage chars) in the "contents" area of a PDF TOC
Status: RESOLVED UPSTREAM
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 0.12.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 20:17 UTC by Flavius Aspra
Modified: 2011-05-28 13:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
demonstrating the bug (568.42 KB, application/pdf)
2011-05-28 00:32 UTC, Flavius Aspra
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Flavius Aspra 2011-05-24 20:17:19 UTC
Version:           0.12.2 (using KDE 4.6.3) 
OS:                Linux

For a working example demonstrating the bug see https://github.com/OriginalCopy/yap-phpro-book. Just clone & make it.

However the downloadable .pdf which I created earlier works: https://github.com/downloads/OriginalCopy/yap-phpro-book/dezvoltare_web_cu_php-03_mai_2011.pdf

So maybe something else has changed in the LaTeX system, the fonts, or something else, BUT okular should handle those changes.

Some other programs I'm using display the pages correctly (for instance evince).

I am using ArchLinux x64, up to date.

Reproducible: Always

Steps to Reproduce:
For a working example demonstrating the bug see https://github.com/OriginalCopy/yap-phpro-book. Just clone & make it.

Actual Results:  
The page numbers contain garbage characters instead of digits, like "ŋđ". It's the same garbage 2-letter string everywhere though.

Expected Results:  
1,2,3,...n :-)
Comment 1 Albert Astals Cid 2011-05-24 21:00:11 UTC
We have very limited time, please provide a link to a pdf showing the problem.
Comment 2 Flavius Aspra 2011-05-28 00:32:45 UTC
Created attachment 60403 [details]
demonstrating the bug
Comment 3 Albert Astals Cid 2011-05-28 13:38:07 UTC
It's a poppler-qt4 bug. I've just fixed it and it will be there in the next poppler release (0.16.6)