[okular] [Bug 486681] Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 --- Comment #2 from aux...@gmail.com --- Created attachment 169257 --> https://bugs.kde.org/attachment.cgi?id=169257=edit PDF file with 2 acronyms demonstrating the issue. The two acronyms are REST, SOAP. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 486681] Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Please provide a simple test file. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 486681] New: Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 Bug ID: 486681 Summary: Display comments created by latex pdfcomment Classification: Applications Product: okular Version: 24.02.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: aux...@gmail.com Target Milestone: --- SUMMARY Comments in PDF files created by latex/xelatex acro/pdfcomment do not display in Okular, although evince displays them. Such comments are useful to display acronyms. STEPS TO REPRODUCE 1. Write a TeX file using latex, acro, pdfcomment, that includes acronyms and pdfcomments. 2. Open it with okular. OBSERVED RESULT The acronym pdfcomment is not displayed when I hover the cursor over the acronym. The mouse cursor changes shape over acronyms, which implies that Okular identifies the string as an acronym. EXPECTED RESULT The acronym pdfcomment is displayed on hover over the acronym. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 486680] New: Okular does not accept blank certificate password when digitally signing PDFs
https://bugs.kde.org/show_bug.cgi?id=486680 Bug ID: 486680 Summary: Okular does not accept blank certificate password when digitally signing PDFs Classification: Applications Product: okular Version: unspecified Platform: Ubuntu OS: Other Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: matej.kova...@telefoncek.si Target Milestone: --- SUMMARY I have installed Okular through Flatpak. I am using Slovenian language version. Since version from 2024-03-12 15:38:44 (Flahub commit: dd1a5b8b88fe55a569a9e38a3855f945be8d9ef46cb42c54884af55892828c39), I can not digitally sign PDF's anymore. Reason: it keeps asking me for certificate password. I don't have one, but when I press enter (and leave input fields empty), it keeps asking for password. STEPS TO REPRODUCE 1. Select Tools- Digitally sign 2. Select certificate and background image 3. Okular asks for a certificate password (if exists) 4. Press enter (because I do not have a password), it keeps asking again... OBSERVED RESULT Cannot digitally sign PDF, because it keeps asking for (nonexistent) password EXPECTED RESULT Should be able to move forward with blank password? SOFTWARE/OS VERSIONS flatpak remote-info --log flathub org.kde.okular All versions after and including this: Commit: dd1a5b8b88fe55a569a9e38a3855f945be8d9ef46cb42c54884af55892828c39 Subject: Update ghostscript & poppler (a178ad4a) Date: 2024-03-12 15:38:44 + -- You are receiving this mail because: You are the assignee for the bug.
[konqueror] [Bug 247817] okular doesn't display correctly the pdf pages in a site
https://bugs.kde.org/show_bug.cgi?id=247817 Christoph Cullmann changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #10 from Christoph Cullmann --- Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann -- You are receiving this mail because: You are on the CC list for the bug.
