Lacking PDF forms i18n support in Evince

[Runar Ingebrigtsen]

There's a character encoding problem filling out forms with localized Evince. The Norwegian characters aren't displayed like they should.

[Runar Ingebrigtsen (ringe)]

Original PDF form.

[Runar Ingebrigtsen (ringe)]

Test case. Form filled out with Norwegian characters, printed from Evince.

[Pedro Villavicencio (pedro)]

Thanks for your report. may you please tell us what you're expecting to see in the pdf? the bug isn't clear to me. Thanks.

[Runar Ingebrigtsen (ringe)]

The large text field below the text "Hvilken vare eller tjeneste klages det på?" in the test case contains the text "Ny bærbar PC kjøpt hos Elkjøp" but this text is rendered as "Ny bÊrbar PC kj¯pt hos Elk¯p"

This is a locale problem. I guess it might have relation to UTF8 and PDF.

[Runar Ingebrigtsen (ringe)]

The wrongly rendered text is what I put in there, using the new support for PDF forms in poppler. All other Norwegian characters in the PDF, which means the text put in by the form's author (the static text), are rendered correctly.

[Pedro Villavicencio (pedro)]

This bug has been reported here:

"There's a character encoding problem filling out forms with localized Evince. The Norwegian characters aren't displayed like they should."

"The large text field below the text "Hvilken vare eller tjeneste klages det på?" in the test case contains the text "Ny bærbar PC kjøpt hos Elkjøp" but this text is rendered as "Ny bÊrbar PC kj¯pt hos Elk¯p"

"The wrongly rendered text is what I put in there, using the new support for PDF forms in poppler. All other Norwegian characters in the PDF, which means the text put in by the form's author (the static text), are rendered correctly."

http://launchpadlibrarian.net/10052805/Klageskjema%20bokmal-1..pdf
http://launchpadlibrarian.net/10052807/evince-print.pdf

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: https://bugs.freedesktop.org/show_bug.cgi?id=12851

[Julien-fhtagn (julien-fhtagn)]

Here are some preliminary findings :

If I force the fields in the document to use the Helvetica font (which is used to render all the others norvegian text in the document), then the fields content is correctly rendered.

Now, the fields in the document use an Arial font (which has usesMacRoman set, don't know if it matters) and the problem appears in Gfx when trying to map the unicode value to the code rendered by the font.
For example, if I enter the character U+00F8 (ø) in a text field, in Gfx.cc:3293, when calling out->drawChar, it will map the code 'f8' to the unicode 'af' when using Arial (and therefore render a '-' instead of 'ø'). When using helvetica, it simply maps 'f8' to 'f8'.

[Mvrable (mvrable)]

This should now be fixed in the development version of poppler (as of commit fb996c46e3c6b56a2c67819620000bcd804aacd6, which adds better support for Unicode and handling different font encodings). Tested with the document attached to the bug report, and it looks to work.

[Pedro Villavicencio (pedro)]

fixed upstream, thanks.

[Sebastien Bacher (seb128)]

the bug is fixed in jaunty now

[Alexander Potashev (aspotashev-deactivatedaccount)]

I have a similar problem: Russian text is not being rendered in forms at all (in Okular, KDE document viewer)

KDE bug report: https://bugs.kde.org/show_bug.cgi?id=193234

[Albert Astals Cid (aacid)]

I'm closing the bug because i've tried to do what KDE bug 193234 says and it doesn't work either in Adobe Reader so i don't think it's our bug, just that that particular PDF is not designed for russian input