Created attachment 58824 [details] pdf form made in LibreOffice PDF forms created with LibreOffice show only latin characters in form fields. Example files in the attachments. PDF forms from some other sources work correctly, i.e. this: http://www.fms.gov.ru/documents/passport/pdf/anketa_new_14u.pdf Viewed in evince, epdfview.
Created attachment 58825 [details] source file for pdf form
It works for me. Tested with LibO 3.4.5 on Windows Vista and with LibO 3.5.2 RC1 on Windows XP. PDF Viewer Acrobat Reader X. If I save the "source file for pdf form" I have russian characters in the form. I can copy russian text from the clipboard into the form (I have no russian keyboard).
(In reply to comment #2) Do you see cyrillic characters rendered? (when focus is not in the field)
Yes.
(In reply to comment #4) > Yes. Could you please see if windows version of evince shows it? Linux versions of evince and epdfview do render cyrillic characters in the form you can get from the link supplied in description. Therefore they are capable of rendering non-latin characters, but fail on LO-created forms.
Evince lists two fonts in LO-generated form: Liberation Sans (embedded subset) Liberation Sans (not embedded) < what does that mean? If I delete form field (leave only text object on the left) and export test document as pdf form, evince will list only: Liberation Sans (embedded subset)
evince-2.32.0.145 (Windows XP) : LibO 3.5.2 RC1 - doesn't work properly: it displays no russian characters, only the latin "abcdefgh" (exactly like that, without the quotation marks). But when when I click on the field, the latin characters disappear and the expected russian characters (the ones displayed on the left side) will be displayed. Tested also with LibO 3.4.5 on Windows XP - the same error. So it seems to be an evince bug. Note: The font "Liberation Sans" is present on my PC (russian characters included), so no substitution is necessary. Embedded subset: fonts, which are embedded in the PDF file, so they can be displayed if they are not installed on your PC. It seems that the russian fonts (on the left side) are embedded, and the fonts in the edit box are not embedded as you must be able to fill them in (i.e. they have to be on the PC).
(In reply to comment #7) It is an evince bug too (failure to use system font in forms), but... If you download pdf file from fms.gov.ru (see description), you will find that evince can display non-latin characters in the fields. That form uses Times New Roman Cyr font which I do not have on my system. But evince shows it in fields, because it is embedded in the form. This leads to two questions: Why LO applies different font sets for text and fields when both use the same Liberation Sans? Why LO embed font for content and does not embed font for fields?
Another pdf font problem: Bug 50879
Hello Vladimir, *, would you be so kind to explain us, how you created the PDF file? If I use your source file, go to "File - Export to PDF..." with "Create PDF Form" enabled on the right sight below "General" in the "PDF Options" window, and just click on "Export", I am able to see the Cyrillic characters in Okular Version 0.14.3 from KDE 4.8.4 under Debian Testing AMD64, after I have clicked on "Show formulars" there. Did you use a different way to find your bug? I have tested it with LO Version: 4.1.0.1 Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155 under Debian Testing AMD64, so I would ask you to test it with a newer version of LO than 3.5.1, if something has changed/improved. It would be nice, if you could change the status of the bug, if it is solved ... ;) And did you you use any other pdf viewer to test the exported PDF or only evince? If it is only an evince problem (like indicated in comment 8), I think, it is not our bug, but an evince one ... ;) Sorry for the inconvenience Thomas.
I can reproduce this on master with Evince but not Adobe Reader. Evince writes to terminal warnings like "warning: layoutText: cannot convert U+0430". The same happens with the fms.gov.ru PDF, and Adobe Reader can’t even open that file. I’m inclined to think it is an evince issue.
I used "Export as PDF" function in File menu. I've retested it with version 4.0.3, viewed with Evince and Adobe Reader. There are no Cyrillic symbols in form in Evince. And funny result with Adobe Reader: it shows only Cyrillic characters, everything else is like password dots. It also gives an error about absence of Liberation Sans font in the OS, although font embedding was enabled during export.
Created attachment 81409 [details] pdf form export 4.0.3
Created attachment 81410 [details] source for pdf form in 4.0.3
Thanks for additional information Reproduced using 4-th attachment test.odt In dialog "PDF Options" was disabled "PDF/A-1a" and enabled "Create PDF form". When opening produced PDF in Okular it asks "Show forms?". If we click on this button then Cyrillic characters shown, if not then not. In Evince are no such option and Cyrillic characters not shown. It looks like problem is in creating form-mode PDF. Ordinary PDFs working correctly.
well, yes. Test file contains simple text field and form text field. Both contain the same string. Simple text field is shown correctly, form field is not.
Created attachment 107869 [details] Pdf form generated from attachment 58825 [details] with 4.1.5.3 I just generated a pdf form using the source in attachment 58825 [details] and the resulting pdf form seems correct. No more "password dots", no more complaints about the missing font. The Cyrillic characters appear in the field.
I've checked your pdf in evince, qpdfview and also xournal. Cyrillic characters are not shown in any of these applications.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Just created a form in LO 5.0.4~rc2 (current version in Debian Testing) Evince and Qpdfview failed to display Cyrillic characters in form fields.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
I retest this bug - it is still here on LibreOffice 5.2.5.1 - when I exporting file to PDF with forms - form values displays only Latin letters, Cyrillic and other non-latin letters are missed and displays as empty space.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still reproducible. Version: 6.2.0.0.alpha0+ Build-ID: 425af6845ebe066c950b0b63f50563e067485f3e CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-DE (de_DE.UTF-8); Calc: threaded
Dear Vladimir, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
No repro 6.2.8 and 7.0+ in Windows with Adobe and PDF-Xchange. I amend the title to say it's just Evince and some readers in Linux. Would be nice to retest with master LO 7.0+.
Dear Vladimir, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I confirm this bug. I downloaded attachment 58825 [details], “Export as PDF…” in LibreOffice, opened the resulting PDF file in Evince. Cyrillic characters are not visible in the form field. If I click on the form field to edit the text, they are visible.
Still no cyrillic characters in unfocused PDF forms saved by Writer. Opened in evince, qpdfview, mupdf. Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: 420(Build:3) CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-DK (en_DK.UTF-8); UI: en-US Debian package version: 4:24.2.0-1 Calc: threaded
The bug still exists. I tried the test in my comment above.