*Poppler* no longer renders certain characters incorrectly
Previously, the *Poppler* library did not map correctly to character code. As a consequence, *Poppler* showed the `fi` string instead of showing the correct glyph, or nothing, if the font did not contain necessary glyphs. With this update, the characters previously replaced with the `fi` string are shown correctly.
Description of problem:
Some characters from PDFDocEncoding are shown as "fi" or are not shown at all when entered into editable forms. This is caused by a bug in poppler. This is now fixed upstream (see https://bugs.freedesktop.org/show_bug.cgi?id=92597).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Get the PDF from https://bugzilla.gnome.org/show_bug.cgi?id=756805#c1
2. Enter "šč" into a field
3. press enter
There is "fifi" shown in the field
There is "š " shown in the field
I should mention that the fact that we don't expect "šč" is caused by the fact that handling of characters not present in PDFDocEncoding is not specified for forms in PDF specification (see https://bugzilla.redhat.com/show_bug.cgi?id=1226260).
Created attachment 1134088 [details]
Find correct glyph or return 0
Created attachment 1134089 [details]
Fix showing of some non-ASCII characters
when can we expect poppler-0.26.5-14.el7
It should be part of Red Hat Enterprise Linux 7.3 update.
Pass on poppler-0.26.5-16.el7
(In reply to Tomas Pelka from comment #7)
> Pass on poppler-0.26.5-16.el7
Tested on all supported arches.
I reported the related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1226260 .
I just tested the new version of poppler (poppler-0.26.5-16.el7) which is included in the latest rhel 7.3 beta and this bug is not fixed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.