I made a note in Okular, but it don't show all Lithuanian letters. Reproducible: Always Steps to Reproduce: 1. In Okular press F6 2. Select second type of notes/anotation 3. write text "Evoliucija nereiškia to, kad, pvz., paukščiams privalėjo atsirasti sparnai arba/ir, kaip ir žmonėms, – sąmonė." Actual Results: In new text box there is no letters: ą, č, ė Expected Results: Text has all letters
Created attachment 73345 [details] example
*** Bug 330527 has been marked as a duplicate of this bug. ***
It's a Poppler issue. I'm sure there is already some Poppler bug about this. Anyway, thanks for caring about Okular :)
*** Bug 310154 has been marked as a duplicate of this bug. ***
https://bugs.freedesktop.org/show_bug.cgi?id=65956
*** Bug 349672 has been marked as a duplicate of this bug. ***
*** Bug 371214 has been marked as a duplicate of this bug. ***
*** Bug 385852 has been marked as a duplicate of this bug. ***
*** Bug 400474 has been marked as a duplicate of this bug. ***
*** Bug 407956 has been marked as a duplicate of this bug. ***
*** Bug 414349 has been marked as a duplicate of this bug. ***
Upstream bug URL: https://gitlab.freedesktop.org/poppler/poppler/issues/362
*** Bug 417643 has been marked as a duplicate of this bug. ***
*** Bug 419414 has been marked as a duplicate of this bug. ***
*** Bug 421452 has been marked as a duplicate of this bug. ***
*** Bug 422044 has been marked as a duplicate of this bug. ***
*** Bug 422118 has been marked as a duplicate of this bug. ***
Is there no hope for this issue to be fixed? It has persisted for nearly 8 years..
Same question from me - on the git there was a discussion about supporting the developer who will try to fix it but without any response. Sorry but Okular editor is useless without this support.
It's still a lack of resources. Okular is still mainly developed by part-time volunteers, and the problem is a bit too challenging for a small side-project.
(In reply to Oliver Sander from comment #20) > It's still a lack of resources. Okular is still mainly developed by > part-time volunteers, and the problem is a bit too challenging for a small > side-project. I disagree, nothing is too challenging for a small side project, fixing that issue is not harder than writing Okular from scratch like we did as part-time developers. Also, as mentioned, this is not something that actually needs fixing on Okular, but on poppler, so please please please stop writing here.
(In reply to Krzysztof Kardas from comment #19) > Same question from me - on the git there was a discussion about supporting > the developer who will try to fix it but without any response. Sorry but > Okular editor is useless without this support. I'll give you back the 0 euros you paid for it if you want.
*** Bug 423258 has been marked as a duplicate of this bug. ***
*** Bug 424708 has been marked as a duplicate of this bug. ***
*** Bug 425290 has been marked as a duplicate of this bug. ***
Sorry Yuri for the duplication and inconvenience. I'd like to take this opportunity, however, to note here what seems to be the upstream (poppler) bug report: https://gitlab.freedesktop.org/poppler/poppler/-/issues/362 So it might be a good idea to join the conversation there in order to better follow any development on this issue. I understand that there are insufficient resources to resolve this bug at the present, and therefore there might be an option to do it by outsourcing and crowdfunding. In that case, people interested might like make a contribution...
As poppler is crappy (in this case), maybe KDE Okular could switch into another engine / library for rendering?
It could, but that would be more work than simply fixing the poppler bug.
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.
*** Bug 425429 has been marked as a duplicate of this bug. ***
*** Bug 427154 has been marked as a duplicate of this bug. ***
*** Bug 427355 has been marked as a duplicate of this bug. ***
*** Bug 427470 has been marked as a duplicate of this bug. ***
*** Bug 431350 has been marked as a duplicate of this bug. ***
*** Bug 431833 has been marked as a duplicate of this bug. ***
*** Bug 431976 has been marked as a duplicate of this bug. ***
*** Bug 432176 has been marked as a duplicate of this bug. ***
*** Bug 432236 has been marked as a duplicate of this bug. ***
Created attachment 135261 [details] attachment-13466-0.html Please remove me for this list JoaoLamares Em 28/01/2021 à(s) 09:17, Yuri Chornoivan <bugzilla_noreply@kde.org> escreveu: https://bugs.kde.org/show_bug.cgi?id=305534 Yuri Chornoivan <yurchor@ukr.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.geno@libero.it --- Comment #38 from Yuri Chornoivan <yurchor@ukr.net> --- *** Bug 432236 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
*** Bug 432435 has been marked as a duplicate of this bug. ***
I don't think it is too chalenging to solve this issue because the Okular version available on Ubuntu 20.04 repositories do accept the special characters. But I would like to use the Flatpak version because it has the dark mode whisch is best for working many hours. I really want that you find a solution soon.
Bug still happening in v20.12.1
Closing again: This is a poppler issue.
*** Bug 433016 has been marked as a duplicate of this bug. ***
*** Bug 434583 has been marked as a duplicate of this bug. ***
(In reply to Oliver Sander from comment #43) > Closing again: This is a poppler issue. What can I do for solving issue? Should i report the bug to popler or is there already there is a bug report in popler?
(In reply to Utku BERBEROĞLU from comment #46) > (In reply to Oliver Sander from comment #43) > > Closing again: This is a poppler issue. > > What can I do for solving issue? Should i report the bug to popler or is > there already there is a bug report in popler? Regretfully, almost nothing at this step unless you have a patch. The bug in poppler can be tracked here (the URL in the header of this bug report): https://gitlab.freedesktop.org/poppler/poppler/issues/362
*** Bug 435244 has been marked as a duplicate of this bug. ***
*** Bug 435857 has been marked as a duplicate of this bug. ***
*** Bug 436173 has been marked as a duplicate of this bug. ***
Seems some progress happened here: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1070#note_897098 However buggy patch was introduced only 4 months ago, meanwhile bug in Okular exist for almost for 10 years. According to comments in https://gitlab.freedesktop.org/poppler/poppler/-/issues/362#note_900139 and https://gitlab.freedesktop.org/poppler/poppler/-/issues/1070#note_897098 , Okalar should show symbols correctly with poppler 20.12.1, fail with newer versions and show correctly again after partial revert of https://gitlab.freedesktop.org/poppler/poppler/-/commit/9db685f379c1c9195b5f0c9a693e7a581e6b214f
*** Bug 436475 has been marked as a duplicate of this bug. ***
*** Bug 436857 has been marked as a duplicate of this bug. ***
*** Bug 436860 has been marked as a duplicate of this bug. ***
*** Bug 436934 has been marked as a duplicate of this bug. ***
(In reply to opensuse.lietuviu.kalba from comment #51) > Seems some progress happened here: > https://gitlab.freedesktop.org/poppler/poppler/-/issues/1070#note_897098 > However buggy patch was introduced only 4 months ago, meanwhile bug in > Okular exist for almost for 10 years. > > According to comments in > https://gitlab.freedesktop.org/poppler/poppler/-/issues/362#note_900139 and > https://gitlab.freedesktop.org/poppler/poppler/-/issues/1070#note_897098 , > Okalar should show symbols correctly with poppler 20.12.1, fail with newer > versions and show correctly again after partial revert of > https://gitlab.freedesktop.org/poppler/poppler/-/commit/ > 9db685f379c1c9195b5f0c9a693e7a581e6b214f Looks like this has been fixed in poppler now. Are the okular devs informed about this so that they can merge it?
(In reply to kojid from comment #56) > (In reply to opensuse.lietuviu.kalba from comment #51) > > Seems some progress happened here: > > https://gitlab.freedesktop.org/poppler/poppler/-/issues/1070#note_897098 > > However buggy patch was introduced only 4 months ago, meanwhile bug in > > Okular exist for almost for 10 years. > > > > According to comments in > > https://gitlab.freedesktop.org/poppler/poppler/-/issues/362#note_900139 and > > https://gitlab.freedesktop.org/poppler/poppler/-/issues/1070#note_897098 , > > Okalar should show symbols correctly with poppler 20.12.1, fail with newer > > versions and show correctly again after partial revert of > > https://gitlab.freedesktop.org/poppler/poppler/-/commit/ > > 9db685f379c1c9195b5f0c9a693e7a581e6b214f > > > Looks like this has been fixed in poppler now. Are the okular devs informed > about this so that they can merge it? It's not really fixed, only a recent regression that broke it a bit more has been fixed. There's nothing to "merge"
*** Bug 437086 has been marked as a duplicate of this bug. ***
*** Bug 437248 has been marked as a duplicate of this bug. ***
*** Bug 437375 has been marked as a duplicate of this bug. ***
*** Bug 437710 has been marked as a duplicate of this bug. ***
*** Bug 439056 has been marked as a duplicate of this bug. ***
*** Bug 439078 has been marked as a duplicate of this bug. ***
*** Bug 439304 has been marked as a duplicate of this bug. ***
This issue is still not resolved.
(In reply to jack6th from comment #65) > This issue is still not resolved. As noted in a previous comment, this is a known issue in the poppler library.
I know there is no problem in Okular and this is a problem of Popler, i think there is a posible way for partial solution. Okular could automaticly change non-ASCII letters to similar ASCII characters. Example: In "Berberoğlu", letter "ğ" could change to g, and at least we can see "Berberoglu" instead of "Berberolu".
This issue is not resolved. I know there is no problem in Okular and this is a problem of Popler, i think there is a posible way for partial solution. Okular could automaticly change non-ASCII letters to similar ASCII characters. Example: In "Berberoğlu", letter "ğ" could change to g, and at least we can see "Berberoglu" instead of "Berberolu".
Utku, Don't do this again.
*** Bug 445674 has been marked as a duplicate of this bug. ***
*** Bug 445919 has been marked as a duplicate of this bug. ***
*** Bug 453983 has been marked as a duplicate of this bug. ***
For what is worth this is now fixed upstream in poppler 22.05.0 You can all wait until your distribution updates to that poppler version or meanwhile use okular from flathub https://flathub.org/apps/details/org.kde.okular