After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 536812 - Text field in PDF form can show only characters from fonts embeded in the PDF file
Text field in PDF form can show only characters from fonts embeded in the PDF...
Status: RESOLVED NOTGNOME
Product: evince
Classification: Core
Component: PDF
2.22.x
Other All
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
: 573011 580085 627024 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-06-05 13:56 UTC by Petr Pisar
Modified: 2017-05-16 21:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
Pdf with form (created by LibreOffice 3.5.4.2) (15.18 KB, application/octet-stream)
2013-02-17 13:47 UTC, f0ma
Details

Description Petr Pisar 2008-06-05 13:56:19 UTC
Please describe the problem:
Writing letter which has no corresponding glyph in embeded fonts results in warning on stderr and charater doesn't display after commiting the change or in printed PS output.

Steps to reproduce:
1. Open PDF with input line from element and focus input line
2. Input character which is not in embeded font
3. Commit the change (and print the file).


Actual results:
During editing system font is used and charater is displayed properly. However after that the input line text is type set by PDF font. If the font has no corresponding glyph, the letter will be omitted and not shown. You get message like "warning: layoutText: cannot convert U+0159".

Expected results:
Evince should be able to emebed new font from system into the PDF and use it instead the original one for the problematic letter or input line or all form elements.

Does this happen every time?
Yes.

Other information:
Acrobat Reader does it (except saving the PDF file). Such a problematic PDF file can be produced with OpenOffice.org because it emebeds only minimal usable subset of the font.
Comment 1 Alexander Kojevnikov 2009-04-28 06:46:22 UTC
*** Bug 573011 has been marked as a duplicate of this bug. ***
Comment 2 Alexander Kojevnikov 2009-04-28 06:46:36 UTC
*** Bug 580085 has been marked as a duplicate of this bug. ***
Comment 3 Germán Poo-Caamaño 2013-02-17 09:10:25 UTC
May you attach a PDF test case?
Comment 4 f0ma 2013-02-17 13:47:29 UTC
Created attachment 236448 [details]
Pdf with form (created by LibreOffice 3.5.4.2)

PDF file example (with form).
Comment 5 Germán Poo-Caamaño 2013-02-18 02:17:39 UTC
Thanks for the test case. It turns out this is a known bug in poppler.

Please, follow the bug report in https://bugs.freedesktop.org/show_bug.cgi?id=17913
Comment 6 Germán Poo-Caamaño 2013-02-18 03:25:11 UTC
*** Bug 627024 has been marked as a duplicate of this bug. ***
Comment 7 Karen Fidanyan 2017-05-16 21:03:34 UTC
Dear users, hello! 
Maybe you'll find this interesting: the reward was set up for fixing this bug. If you are concerned about this bug, you are welcome to support this initiative or try to fix it.
More details about the reward are here: 
https://freedomsponsors.org/issue/807/problem-with-cyrillic-and-japanese-at-pdf-forms-evince-okular