Bug 345897

Summary:	Wrong display of some math characters in particular document
Product:	[Applications] okular	Reporter:	Sergey Kostyuk <ks.hot.ua>
Component:	PDF backend	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED NOT A BUG
Severity:	minor	CC:	aacid, simonandric5, yurchor
Priority:	NOR
Version First Reported In:	0.21.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	the file for posterity Screenshot from arch system of second sample file (file http://goo.gl/ThlXl9) Screenshot from ubuntu system of second sample file (file http://goo.gl/ThlXl9) Arch - font properties of document with existing symbol.ttf font Arch - font properties of document with deleted symbol.ttf font file

Description Sergey Kostyuk 2015-04-05 18:34:43 UTC

Good day.

Some symbols in particular PDF document (generated by PageMaker 6.5 but I don't know if it matters) are displayed wrong by Okular. For example symbol ≤ looks like " and symbol π - like ≠. But only looks so. If we select those symbols and copy them somewhere else (for example, to .txt document, terminal, anywhere) - we will get ≤ and π respectively, as must to be.

Sorry for my English.

Sorry for my English

Reproducible: Sometimes

Steps to Reproduce:
0. Download this file (one page from problem pdf document): http://goo.gl/FdZLwF
1. Open it with Okular
2. Open it with another PDF viewer (I used Chromium build-in PDF Viewer and Google Docs web viewer)
3. Compare

AND

1. Open erroneous document in Okular
2. Select and copy some text to LibreOffice Writer or Sublime Text, for example
3. Compare result with displayed page in Okular

Actual Results:  
In Okular symbol ≤ looks like " and symbol π - like ≠, unlike in another viewers. But symbols in copied text from Okular to another text editor looks normal.

Expected Results:  
Symbol must ≤ look like ≤ and symbol π - like π

Properties of the original document: http://imgur.com/cZxtuw8

Comment 1 Sergey Kostyuk 2015-04-05 18:56:27 UTC

Another sample (PDF page), similar problem with sum symbol: http://goo.gl/ThlXl9

Comment 2 Yuri Chornoivan 2015-04-05 19:24:24 UTC

Looks fine here (okular 0.22.60, poppler 0.28).

Can you check what your version of poppler is ("pdftotext -v")? Is it possible to test it with another version?

Thanks in advance for your answers.

Comment 3 Albert Astals Cid 2015-04-05 19:34:49 UTC

Created attachment 91900 [details]
the file for posterity

Comment 4 Albert Astals Cid 2015-04-05 19:35:11 UTC

Please attach a screenshot highlighting where the problem is

Comment 5 Sergey Kostyuk 2015-04-05 19:44:56 UTC

Created attachment 91901 [details]
Screenshot from arch system of second sample file (file http://goo.gl/ThlXl9)

Comment 6 Sergey Kostyuk 2015-04-05 19:47:13 UTC

Created attachment 91902 [details]
Screenshot from ubuntu system of second sample file (file http://goo.gl/ThlXl9)

Comment 7 Sergey Kostyuk 2015-04-05 19:48:15 UTC

Original report was created from Arch system with okular 0.21.3 and poppler 0.31.0. And just installed Okular on Ubuntu system (okular 1.19.3, poppler 0.24.5) - document looks well. Screenshots attached. 

Can I provide more information? Thanks.

Comment 8 Albert Astals Cid 2015-04-05 22:19:25 UTC

Do you have poppler-data?

Comment 9 Sergey Kostyuk 2015-04-06 19:24:59 UTC

No, I had't. But just installed poppler-data 0.4.7-1 - no change, still erroneous display.

Comment 10 Albert Astals Cid 2015-04-07 20:22:49 UTC

compare the file->properties->fonts contents, and attach the screenshots here

Comment 11 Sergey Kostyuk 2015-04-08 16:42:18 UTC

Created attachment 91949 [details]
Arch - font properties of document with existing symbol.ttf font

Comment 12 Sergey Kostyuk 2015-04-08 16:43:01 UTC

Created attachment 91951 [details]
Arch - font properties of document with deleted symbol.ttf font file

Comment 13 Sergey Kostyuk 2015-04-08 16:49:38 UTC

Many thanks, issue solved, not an Okular bug. And sorry for wasted time.

The problem was in one font file (symbol.ttf), copied from Windows font folder long time ago. I just needed to delete it - and everything backed to normal.