https://bugs.kde.org/show_bug.cgi?id=305534
--- Comment #29 from opensuse.lietuviu.ka...@gmail.com --- According to upstream bug comment, maybe problem is not rendering, but SAVING of annotation incorrectly? See comment by Triffid Hunter <https://gitlab.freedesktop.org/poppler/poppler/-/issues/362#note_78739>: PS I found a kludge: Open the saved PDF in Google Chrome's built-in viewer, select the affected fields, cut all text (clearing the field), focus another field, then paste it back into the relevant field, and non-ascii characters then become visible and can be printed/transmitted as expected - and are even visible when I 'print to PDF' from chrome and open the result in okular! Apparently the way that okular stores non-ascii in form fields affects chrome, but when non-ascii is entered into an empty form field in chrome, chrome handles it correctly. -- You are receiving this mail because: You are the assignee for the bug.
