[okular] [Bug 452017] Feature to rename open PDF files with F2 keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=452017 --- Comment #4 from andreas.naum...@kdemail.net --- When I select "save as", I get a "save as"-dialoge. That dialog allows to save the file with a new name AND rename existing files. In particular, if I press F2 in the "save as" dialog, I get the "rename element" dialog for the current file. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449717] When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.
https://bugs.kde.org/show_bug.cgi?id=449717 andreas.naum...@kdemail.net changed: What|Removed |Added CC||andreas.naum...@kdemail.net --- Comment #3 from andreas.naum...@kdemail.net --- In you videos, you show two pages side by side. Does it help, if you disable the "continous view" and show only one page? In that configuration, okular stays at the page and zooms only. If I enable the view mode "overview", I get your behavior. In that configuration, I would rather ask, what zoom in means to the developer. Looks to me, like okular increases the view starting from the upper left corner. It would feel more natural, if okular zooms into the area next to the finger position. Do we know the mouse position, when zooming? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 452017] Feature to rename open PDF files with F2 keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=452017 andreas.naum...@kdemail.net changed: What|Removed |Added CC||andreas.naum...@kdemail.net --- Comment #2 from andreas.naum...@kdemail.net --- Are you really talking about the filename, or the pdf title? If you are talking about the filename, than what is wrong with "save as" in the menu below file? On my system it has the shortcut "ctrl-shift-s". So, maybe the user could simply set a user-defined short cut for that? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 443801] Feature Request: Preview annotations on annotation tab
https://bugs.kde.org/show_bug.cgi?id=443801 mineirodomu...@gmail.com changed: What|Removed |Added CC||mineirodomu...@gmail.com --- Comment #1 from mineirodomu...@gmail.com --- Would this be an example of the feature requested? https://i.ibb.co/k5WgTvH/Screenshot-2022-03-18-20-19-15.png -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451519] Typewriter ignores rotation
https://bugs.kde.org/show_bug.cgi?id=451519 --- Comment #1 from jakob...@gmx.de --- Created attachment 147505 --> https://bugs.kde.org/attachment.cgi?id=147505=edit A screenshot that shows the problem -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451519] New: Typewriter ignores rotation
https://bugs.kde.org/show_bug.cgi?id=451519 Bug ID: 451519 Summary: Typewriter ignores rotation Product: okular Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: jakob...@gmx.de Target Milestone: --- Created attachment 147504 --> https://bugs.kde.org/attachment.cgi?id=147504=edit A testfile that needs to be rotated Steps to reporduce: 1. Open a Document 2. Rotate it 3. Add a Typewriter Annotation You will see, that the Typewriter still uses the old direction, which results in vertical text. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 370382] Using non-default size for custom stamp pixelates the stamp
https://bugs.kde.org/show_bug.cgi?id=370382 thomas.ramsa...@gmx.de changed: What|Removed |Added CC||thomas.ramsa...@gmx.de --- Comment #2 from thomas.ramsa...@gmx.de --- I know this is old.. but for me this bus is still present in version 21.12.2 . It would be very nice to be able to add a high-res signature with the custom stamp feature. The stamp/signature is pixelated for me for both options: click or click/hold/drag. For click only: It shows clear on click, yet pixelates on release. It does not have its full resolution when zoomed in.. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451113] Add Shortcut CRTL-W for closing tabs
https://bugs.kde.org/show_bug.cgi?id=451113 --- Comment #2 from m.w...@web.de --- I checked. Okular was not in the central shortcut settings. I added it, then shortcut started to work. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451113] Add Shortcut CRTL-W for closing tabs
https://bugs.kde.org/show_bug.cgi?id=451113 andreas.naum...@kdemail.net changed: What|Removed |Added CC||andreas.naum...@kdemail.net Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from andreas.naum...@kdemail.net --- I have version 20.12.3, which is older. It does provide a shortcut for "closing". Can you please check your settings for closing? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449043] underline
https://bugs.kde.org/show_bug.cgi?id=449043 andreas.naum...@kdemail.net changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #9 from andreas.naum...@kdemail.net --- The commit 894b47409ecbecca8735da63629030e14aa520ca in poppler fixes this issue. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451113] New: Add Shortcut CRTL-W for closing tabs
https://bugs.kde.org/show_bug.cgi?id=451113 Bug ID: 451113 Summary: Add Shortcut CRTL-W for closing tabs Product: okular Version: 21.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: m.w...@web.de Target Milestone: --- In browsers and Dolphin there is CRTL-W for closing the current tab. In Okular this short cut does not exist. I think it makes sense to make it work here too. There may be other tab handling short cuts which I do not know, but make sense to implement here too. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451060] New: don't force user to go command-line to get SmartCard signing to work.
https://bugs.kde.org/show_bug.cgi?id=451060 Bug ID: 451060 Summary: don't force user to go command-line to get SmartCard signing to work. Product: okular Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: ludwig.m...@gmail.com Target Milestone: --- Add GUI button in Settings -> Configure Backends -> PDF: ["Add Security Device"] *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Before I resolved my problem, the okular error message when trtying to add a signature was cryptic. It found the Certificate Database, but it didnt automatically contain the security device (just like say firefox doesnt out of the box), but Okular does not provide a GUI means of adding the security device .so module (whereas Firefox does). Currently the user is expected to have already added the to the certificate database, say through firefox, where there is a button security devices, and then add/load where you can give: * a pretty name for the security device * the location of the relevant security device library (in my case /usr/lib/opensc-pkcs11.so This can be found by running say: p11-kit list-modules and then using find / -name on the opensc .so Wondering what firefox was doing under the hood, I found it at: https://gist.github.com/PhilipSchmid/a82b9642e1ec2bf2d16823d72cffc589 so I ran the following command: modutil -dbdir $HOME/.pki/nssdb/ -add "Mijn eID" -libfile "/usr/lib/opensc-pkcs11.so" -force and probably unnecessarily also the command modutil -dbdir $HOME/.pki/nssdb/ -enable "Mijn eID" -force I say unnecessarily because according to arch-wiki instructions for FireFox and Chromium: https://wiki.archlinux.org/title/Smartcards#Configuration It seems unneccesary to run the -enable command for Chromium (whereas FireFox does these commands under the hood, and shows GUI method, what I request for Okular) I would also like to note that it doesn't seem necessary to install the government supplied middleware at all! OpenSC works. The only weird thing was that I had to select the authentication certificate, it seemed to ask an extra password for the signing certificate but my PIN code did not work! Whereas it worked for the authentication certificate... I think the middlewares of all the different countries are just de-quirking the non-compliance with smartcard standards? my apologies for my messy submisssion, I am not familiar with reporting bugs/wishes... STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393811] Inconsistent behaviour in saving comments
https://bugs.kde.org/show_bug.cgi?id=393811 --- Comment #17 from mineirodomu...@gmail.com --- Hi Albert, Thanks for the quick reply. I plan to have the following workflow: 1- select the region 2- once the mouse is released 2.1- create the note 2.2- open inline note editor 3- the user can enter the text like when it is editing an inline note 4- the user might close the editor using ESC I attached some screenshots that I hope will give a better idea of this workflow. An effect of this change would be that the area initially chosen by the user would define the size of the note. Currently, Okular readjusts the area of the note depending on the size of the text entered, but this might lead the note to hide something that might be important for the user. In the example attached, the idea is that the user could define the note by the side of the title, which currently covers the title, in the new workflow that would not happen. Thanks for the hard work. Okular is my favorite way of taking notes. Cheers, -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393811] Inconsistent behaviour in saving comments
https://bugs.kde.org/show_bug.cgi?id=393811 --- Comment #16 from mineirodomu...@gmail.com --- Created attachment 147227 --> https://bugs.kde.org/attachment.cgi?id=147227=edit expected result of the second note -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393811] Inconsistent behaviour in saving comments
https://bugs.kde.org/show_bug.cgi?id=393811 --- Comment #15 from mineirodomu...@gmail.com --- Created attachment 147226 --> https://bugs.kde.org/attachment.cgi?id=147226=edit current note with unexpected size -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393811] Inconsistent behaviour in saving comments
https://bugs.kde.org/show_bug.cgi?id=393811 --- Comment #14 from mineirodomu...@gmail.com --- Created attachment 147225 --> https://bugs.kde.org/attachment.cgi?id=147225=edit selecting area for second note -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451010] New: PDF Document contains a save button which does not work
https://bugs.kde.org/show_bug.cgi?id=451010 Bug ID: 451010 Summary: PDF Document contains a save button which does not work Product: okular Version: 21.12.2 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: andreaswu...@gmx.de Target Milestone: --- Created attachment 147224 --> https://bugs.kde.org/attachment.cgi?id=147224=edit Document with the save "Speichern" button on the second page. STEPS TO REPRODUCE 1. Open the attached document 2. On the bottom of the second page there is a "Speichern" (save) Button 3. click on it - nothing happens I observed this behaviour on Windows using the latest okular version from the windows store. Unfortunately i cannot test with a linux version, because i am running Kubuntu 20.4 which contains a quite old okular, but there it does not work as well. The same document contains also a print button which does not work, but this has been fixed lately (see https://bugs.kde.org/show_bug.cgi?id=448791) OBSERVED RESULT => nothing happens.. EXPECTED RESULT => save dialog should be opened -> at least i can observe this behaviour with adobe acrobat SOFTWARE/OS VERSIONS Windows: Window 10 Okular 21.12.2 KDE Frameworks 5.90.0 QT 5.15.2 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393811] Inconsistent behaviour in saving comments
https://bugs.kde.org/show_bug.cgi?id=393811 --- Comment #13 from mineirodomu...@gmail.com --- Created attachment 147223 --> https://bugs.kde.org/attachment.cgi?id=147223=edit note with text -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393811] Inconsistent behaviour in saving comments
https://bugs.kde.org/show_bug.cgi?id=393811 --- Comment #12 from mineirodomu...@gmail.com --- Created attachment 147222 --> https://bugs.kde.org/attachment.cgi?id=147222=edit text entry using note editor -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393811] Inconsistent behaviour in saving comments
https://bugs.kde.org/show_bug.cgi?id=393811 --- Comment #11 from mineirodomu...@gmail.com --- Created attachment 147221 --> https://bugs.kde.org/attachment.cgi?id=147221=edit note created and note editor opened -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393811] Inconsistent behaviour in saving comments
https://bugs.kde.org/show_bug.cgi?id=393811 --- Comment #10 from mineirodomu...@gmail.com --- Created attachment 147220 --> https://bugs.kde.org/attachment.cgi?id=147220=edit selecting note shape/area -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393811] Inconsistent behaviour in saving comments
https://bugs.kde.org/show_bug.cgi?id=393811 mineirodomu...@gmail.com changed: What|Removed |Added CC||mineirodomu...@gmail.com Platform|Fedora RPMs |Ubuntu Packages --- Comment #8 from mineirodomu...@gmail.com --- Hello everyone, I tend to agree David, so I would like to raise this issue again. It seems inconsistent Okular adds new inline and pop-up notes. In particular, I like that I am able to add a new pop-up note without having to click on a button, just pressing 'esc' after I finished typing the note. However, if I am creating an in-line note I always need to click on the OK button, since there is no shortcut to confirm the text. I did some digging end found how this is done: https://invent.kde.org/graphics/okular/-/blob/master/part/pageviewannotator.cpp#L203 I wonder if I could work on this changes and prepare a pull request. Cheers, -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 450906] New: When using 'okular --unique', a information is given, "There is already a unique Okular instance running. This instance won't be the unique one."
https://bugs.kde.org/show_bug.cgi?id=450906 Bug ID: 450906 Summary: When using 'okular --unique', a information is given, "There is already a unique Okular instance running. This instance won't be the unique one." Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: x...@bupt.edu.cn Target Milestone: --- Created attachment 147163 --> https://bugs.kde.org/attachment.cgi?id=147163=edit a information after runing "okular --unique". However, there is no okular window opened before SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. run 'okular --unique' OBSERVED RESULT a information after runing "okular --unique", "There is already a unique Okular instance running. This instance won't be the unique one". However, there is no okular window opened before EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 450098] PDF Form Fields are not propagated to other (non editable fields) -
https://bugs.kde.org/show_bug.cgi?id=450098 --- Comment #4 from andreaswu...@gmx.de --- Created attachment 147154 --> https://bugs.kde.org/attachment.cgi?id=147154=edit second document with not working input field propagation. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 450098] PDF Form Fields are not propagated to other (non editable fields) -
https://bugs.kde.org/show_bug.cgi?id=450098 --- Comment #3 from andreaswu...@gmx.de --- Hi, i just encountered a new document which also does propagate the input field values to different form fields. On the very first page you can enter Nachname, Rufname and Geburtsdatum. When values are entered here, the values should be propagated to the page 4 and 5, which contain the same input fields (however this time the input fields are editable). -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 382246] Missing Adobe Acrobat printing functionality / features /options
https://bugs.kde.org/show_bug.cgi?id=382246 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 450098] PDF Form Fields are not propagated to other (non editable fields) -
https://bugs.kde.org/show_bug.cgi?id=450098 --- Comment #2 from andreaswu...@gmx.de --- I have also with the Okular Windows Version 21.12.2 - it did not work there as well. I do not have an up to date Linux version - but i assume, it does not work there as well. Version 21.12.2 Using Poppler 22.02.0 KDE Frameworks Version 5.90.0 Qt Version 5.15.2 (built against 5.15.2) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 450334] "Search for... in this document" item in Text Selection context menu does not truncate new lines
https://bugs.kde.org/show_bug.cgi?id=450334 andreas.naum...@kdemail.net changed: What|Removed |Added CC||andreas.naum...@kdemail.net -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 450099] New: PDF Form fields should have a more distinguisable color
https://bugs.kde.org/show_bug.cgi?id=450099 Bug ID: 450099 Summary: PDF Form fields should have a more distinguisable color Product: okular Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: andreaswu...@gmx.de Target Milestone: --- Created attachment 146639 --> https://bugs.kde.org/attachment.cgi?id=146639=edit Document with form fields Hi, pdf form fields should have a more distinguisable color, so that they can be more easily identified. Clicking on the Hide Forms / Show Forms button - make the input fields of the form editable - however they are not that easily identifiable. It would be nice if the input fields could have a different background color so that they can be much easier identified. Usually the documents have a white background color - the input fields have almost the same color (no real contrast from the background color) Acrobat show the input fields with a different background color - so the input fields can easily be identified. STEPS TO REPRODUCE 1. Open the attached document and view the form fields when they are showing. OBSERVED RESULT no real contrast in the background color. EXPECTED RESULT better contrast for the background color of the input fields, so they can be easier identified. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.4 (available in About System) KDE Plasma Version: Kubuntu 20.4 KDE Frameworks Version: 5.68 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 450098] PDF Form Fields are not propagated to other (non editable fields) -
https://bugs.kde.org/show_bug.cgi?id=450098 --- Comment #1 from andreaswu...@gmx.de --- Created attachment 146638 --> https://bugs.kde.org/attachment.cgi?id=146638=edit PDF Document with the form fields. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 450098] New: PDF Form Fields are not propagated to other (non editable fields) -
https://bugs.kde.org/show_bug.cgi?id=450098 Bug ID: 450098 Summary: PDF Form Fields are not propagated to other (non editable fields) - Product: okular Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: andreaswu...@gmx.de Target Milestone: --- Hi, i have a PDF form for which you can edit the form fields on the first page. The page 1 reappears as page 3 (also in german) and again on page 5 (this time in french). So so basically enter the form values on page 1 and they should be propagated the the non editable ?form fields? on page 3 and page 5 - so you only have to enter them once. This is at least the way it works with Adobe Acrobat. Okular just does not do anything. No form fields are propagated. STEPS TO REPRODUCE 1. Open attached document. Enter values in the Form for fields e.g. with label "Name und Vorname oder Firma" or "Beruf / Rechtsform" OBSERVED RESULT On page 3 and 5 we have the same labels (input fields - not editable) - here the entered values from the first page are supposed to show up (works with Adobe Acrobat), but they do not. EXPECTED RESULT Entered values from the first page (from the various input fields) - there is also a date field - should be propagated to the corresponding fields on page 3 and 5. I am using okular 1.9.3 (as provided with Kubuntu 20.4) - but i also tested this with the latest Okular version from the windows store - it did not work there as well. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.4 (available in About System) KDE Plasma Version: Kubuntu 20.4 KDE Frameworks Version: 5.68 Qt Version: 5.12.8 If you need more information - please tell me. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449043] underline
https://bugs.kde.org/show_bug.cgi?id=449043 --- Comment #8 from andreas.naum...@kdemail.net --- It is related to the bug in poppler: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1215 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449596] Opening PDF with Okular has application title "ISE Opener - Okular"
https://bugs.kde.org/show_bug.cgi?id=449596 andreas.naum...@kdemail.net changed: What|Removed |Added CC||andreas.naum...@kdemail.net --- Comment #5 from andreas.naum...@kdemail.net --- Are you sure, that you did not mixup the file pdf names?The titles given by the pdfs are **ISE Opener** and **Book Opener**, but in different orders than your report titles suggest. To me that does not look like an error in okular, but a mistake in the pdfs metadata. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 197726] Show annotations pop-up text in the reviews sidebar
https://bugs.kde.org/show_bug.cgi?id=197726 beanf...@gmail.com changed: What|Removed |Added CC||beanf...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449718] underline last letter
https://bugs.kde.org/show_bug.cgi?id=449718 --- Comment #3 from andreas.naum...@kdemail.net --- (In reply to Albert Astals Cid from comment #1) > Can you attach a video/gif of that (or put it in imgur)? I can underline > just fine. It seems to happen only in a specific cirumstance: 1. open the test file autotests/data/file1.pdf 2. make sure, that the sidebar is shown (settings -> show sidebar) 3. set the zoom level to 400 % (that is a minimal value for me. with larger zoom levels, the problem occurs, with smaller it disapears. My display resolution is 1920x1080) 4. zoom to the end of the first line 5. close okular 6. restart okular from the commandline with the same file as only argument (for me, it shows the file at the end of the first line) 7. select "underline annotation" 8. try to underline starting from the word "file" to the end (for me the underline stops at the letter a in "was") 9. reset the zoom level to 100 % 10. try to underline the full line (the underline stops at the letter "a" again). But one can select the first and the second line together, which includes the end of the first line and the last character. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449718] underline last letter
https://bugs.kde.org/show_bug.cgi?id=449718 --- Comment #2 from andreas.naum...@kdemail.net --- Created attachment 146361 --> https://bugs.kde.org/attachment.cgi?id=146361=edit video showing all steps -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449718] underline last letter
https://bugs.kde.org/show_bug.cgi?id=449718 andreas.naum...@kdemail.net changed: What|Removed |Added CC||andreas.naum...@kdemail.net -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449718] New: underline last letter
https://bugs.kde.org/show_bug.cgi?id=449718 Bug ID: 449718 Summary: underline last letter Product: okular Version: 21.12.1 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: andreas.naum...@kdemail.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open pdf 2. select underline annotation 3. try to select a line including the last letter OBSERVED RESULT underline stops at the letter before the last, except when selecting the next line, too EXPECTED RESULT underlined letters in one line. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.11.0-44.generic (X11) (available in About System) KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION This might be related to https://bugs.kde.org/show_bug.cgi?id=449043 . As a test, I choose the file autotests/data/file1.pdf from the okular sources. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 263732] add a commandline flag for dynamically specifying reverse-search editor command
https://bugs.kde.org/show_bug.cgi?id=263732 andreas.naum...@kdemail.net changed: What|Removed |Added CC||andreas.naum...@kdemail.net --- Comment #2 from andreas.naum...@kdemail.net --- The current implementation has a side effect. If one sets the external editor through the commandline, the change will be written to the configuration. Thus when opening other pdfs later, the external editor from the last command-line setting will be used. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449043] underline
https://bugs.kde.org/show_bug.cgi?id=449043 andreas.naum...@kdemail.net changed: What|Removed |Added Status|CONFIRMED |ASSIGNED CC||andreas.naum...@kdemail.net -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449572] New: Okular sidebar tabs are not consistent with other styles like Gwenview
https://bugs.kde.org/show_bug.cgi?id=449572 Bug ID: 449572 Summary: Okular sidebar tabs are not consistent with other styles like Gwenview Product: okular Version: 21.12.2 Platform: Neon Packages OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: marcwalling...@gmail.com Target Milestone: --- SUMMARY Okular sidebar tabs have a different visual design than sidebar tabs used in Gwenview. Assuming the latter is the desired version, then Okular is not visually consistent. STEPS TO REPRODUCE 1. Open Okular 2. Look at the Sidebar 3. Compare to Gwenview's sidebar OBSERVED RESULT Okular sidebar is not consistent with Gwenview sidebar EXPECTED RESULT Okular sidebar should be consistent with Gwenview sidebar SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449448] Pre-render the subsequent page, and speed-up the large PDF rendering (even the text PDFs are too slow at the moment)
https://bugs.kde.org/show_bug.cgi?id=449448 --- Comment #7 from mikeb...@gmail.com --- (In reply to Albert Astals Cid from comment #6) > Super weird decision, the desktop UI is not mobile optimized, but whatever, > that's out of scope. If by mobile UI, you mean the UI found in Android app: Android apps aren't compatible with Linux (without some emulation). For Linux, there's a desktop Okular. PostmarketOS, like the other Pinephone-compatible distros, provide the mobile UI of an OS itself - i.e. Phosh is "mobile GNOME", Plasma Mobile is a "mobile KDE" - but the apps themselves are the regular desktop Linux apps... Or the Okular mobile UI is available for "desktop Linux" too? (In reply to Albert Astals Cid from comment #6) > I have bad news for you, we already prerender the subsequent page. If it's > not happening for you something is broken on your end. > > Maybe you chose "low memory usage" on the settings? No, I didn't change any settings -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449448] Pre-render the subsequent page, and speed-up the large PDF rendering (even the text PDFs are too slow at the moment)
https://bugs.kde.org/show_bug.cgi?id=449448 --- Comment #5 from mikeb...@gmail.com --- (In reply to Albert Astals Cid from comment #4) > Why would PostmarketOS a mobile OS, use the desktop variant of Okular? > Makes no sense to me. Technically this is a full-featured Linux, and it's possible to use Pinephone as a regular Linux desktop together with a dock adapter. (In reply to Albert Astals Cid from comment #4) > Anyhow, it's easy to solve, can you please attach a screenshot? Here's a screenshot - https://imgur.com/a/kW3jJnW , hope it could help to determine if that's really a desktop or mobile Okular UI -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449448] Pre-render the subsequent page, and speed-up the large PDF rendering (even the text PDFs are too slow at the moment)
https://bugs.kde.org/show_bug.cgi?id=449448 --- Comment #3 from mikeb...@gmail.com --- (In reply to Albert Astals Cid from comment #2) > Just to be clear, you're speaking about the Okular *mobile* interface and not > the desktop one, right? I am using a Pinephone, which runs a PostmarketOS (https://postmarketos.org/) based on Alpine Linux (https://alpinelinux.org/). Therefore, I think I use a desktop interface: just constrained by a small screen size and may be affected by lower hardware performance. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449448] Pre-render the subsequent page, and speed-up the large PDF rendering (even the text PDFs are too slow at the moment)
https://bugs.kde.org/show_bug.cgi?id=449448 mikeb...@gmail.com changed: What|Removed |Added Component|PDF backend |general --- Comment #1 from mikeb...@gmail.com --- Moving to "general" because this pre-rendering may be related not only to PDFs -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449448] New: Pre-render the subsequent page, and speed-up the large PDF rendering (even the text PDFs are too slow at the moment)
https://bugs.kde.org/show_bug.cgi?id=449448 Bug ID: 449448 Summary: Pre-render the subsequent page, and speed-up the large PDF rendering (even the text PDFs are too slow at the moment) Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: mikeb...@gmail.com Target Milestone: --- I have a 70MB PDF file, which is mostly text. It renders too slow, and I have to wait sometimes almost half minute when I simply switch a page. The near pages should be rendered in advance at background mode to save the time, and in general this should be optimized Platform: Alpine Linux / PostmarketOS running on a Pinephone with KDE Plasma Mobile -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449267] Feature request: Multiple selections using Ctrl+selecting text like LibreOffice or Firefox allow.
https://bugs.kde.org/show_bug.cgi?id=449267 amanita+kdeb...@mailbox.org changed: What|Removed |Added Keywords||efficiency, usability -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449267] New: Feature request: Multiple selections using Ctrl+selecting text like LibreOffice or Firefox allow.
https://bugs.kde.org/show_bug.cgi?id=449267 Bug ID: 449267 Summary: Feature request: Multiple selections using Ctrl+selecting text like LibreOffice or Firefox allow. Product: okular Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** It would be really handy to be able to copy a set of lines from a PDF by pressing Ctrl. LibreOffice and Firefox allow this. OBSERVED RESULT You can only select one thing at once EXPECTED RESULT Being able to select multiple parts and copying them into one Text. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 449187] New: Highligthing some latex equations also takes highlights half the line below
https://bugs.kde.org/show_bug.cgi?id=449187 Bug ID: 449187 Summary: Highligthing some latex equations also takes highlights half the line below Product: okular Version: 21.12.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: ultrap...@gmail.com Target Milestone: --- Created attachment 145946 --> https://bugs.kde.org/attachment.cgi?id=145946=edit Wrong highlighting SUMMARY When using PDFs with Latex equations, highlighting text can sometimes result in half the line below the highlighted text to also be highlighted. This seems to happen only for certain characters and not for all equations. See for example this pdf: https://arxiv.org/pdf/hep-lat/0312022.pdf OBSERVED RESULT See attachment. Note that avoiding the "+" symbol and the spaces around it doesn't highlight the line below, and produce the correct behavior. However, the "+" symbol is not the only symbol to produce the bug. EXPECTED RESULT The line with the words "transition because" in the attachment should no be half highlighted, and only with "(3+1)d E(6)" should be highlighted. SOFTWARE/OS VERSIONS Windows 10 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 448930] New: Improve inline notifications' appearance
https://bugs.kde.org/show_bug.cgi?id=448930 Bug ID: 448930 Summary: Improve inline notifications' appearance Product: okular Version: 21.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: aron...@gmail.com Target Milestone: --- Created attachment 145736 --> https://bugs.kde.org/attachment.cgi?id=145736=edit mockzp Currently, inline notifications are not too pretty and kind of merge together with the document. There could be a separate panel which contains them and more padding around them. (I attached one idea for improving them) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 448791] New: PDF Document contains a print button which does not work
https://bugs.kde.org/show_bug.cgi?id=448791 Bug ID: 448791 Summary: PDF Document contains a print button which does not work Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: andreaswu...@gmx.de Target Milestone: --- Created attachment 145648 --> https://bugs.kde.org/attachment.cgi?id=145648=edit Sample Document with print button. STEPS TO REPRODUCE 1. Open the attached document 2. In the lower right corner is a print button (label: "Drucken") 3. click on it I observed the same behaviour on Windows using the latest okular version from the windows store. Maybe this behaviour was / is fixed in the latest okular version - unfortunately i only do have a rather old version. OBSERVED RESULT => nothing happens.. EXPECTED RESULT => print dialog should be opened -> at least i can observe this behaviour with acrobat and master-pdf-editor. SOFTWARE/OS VERSIONS Windows: Windows 11 Linux/KDE Plasma: Kubuntu 20.2 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 437774] Document sometimes reloads after saving annotations
https://bugs.kde.org/show_bug.cgi?id=437774 pbs3...@googlemail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from pbs3...@googlemail.com --- As I no longer have to mark supervision work, I am no longer spending many hours per week creating and saving annotations in okular, so I haven't actually triggered this bug once since the last comment. It's probably still there, but I have no need to fix it. Since nobody else seems to care, and it probably only happens in rare conditions on old computers anyway, it can probably be closed. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 448545] Remove signatures
https://bugs.kde.org/show_bug.cgi?id=448545 --- Comment #2 from aron...@gmail.com --- (In reply to Albert Astals Cid from comment #1) > I see no reason at all for why would be of any use. Please explain why it > would be great with more detail. My use case is an official governmental signing service only accepts documents that are not already signed, so anyone who needs to use this service would need it from time to time. and I guess there are other signature software which don't work if a document is already signed -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 448545] New: Remove signatures
https://bugs.kde.org/show_bug.cgi?id=448545 Bug ID: 448545 Summary: Remove signatures Product: okular Version: 21.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: aron...@gmail.com Target Milestone: --- It'd be great if there was an option to remove a signature from an already signed document. (Technically you already can by printing to PDF, but 99% of users including me doesn't realise that) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 448258] HOME and END key shortcuts are inconsistent
https://bugs.kde.org/show_bug.cgi?id=448258 --- Comment #5 from andreas.d.k...@gmail.com --- I'd prefer that Home and End are set as default for whole document scrolling. It's also the default for: evince, firefox, chromium Even though not everywhere, for example xpdf does it exactly in the way as you suggest with ctrl (document scrolling), without ctrl (page scrolling) In my opinion, the default key shortcuts should not surprise the user for a good user experience. And me, for example, was quite surprised about the default shortcut. Even if an accidental press of Home or End happens, the user can still reason about it and act accordingly (by changing the default shortcut bindings or taking more care about what key to press). In summary, I'm not sure if breaking consistency over all KDE applications only for Okular for a (maybe not so common) use-case is a good idea, as the defaults can be changed. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 448360] New: Can't configure path in PDF Backends on Windows
https://bugs.kde.org/show_bug.cgi?id=448360 Bug ID: 448360 Summary: Can't configure path in PDF Backends on Windows Product: okular Version: 21.12.1 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: andreas.h...@weizenbaum-institut.de Target Milestone: --- Created attachment 145403 --> https://bugs.kde.org/attachment.cgi?id=145403=edit bug_okular_signature Okular Version 21.12.1 Windows 10 S/MIME Certificate is installed on Windows own certmgr, Firefox nss DB and Thunderbird nss DB STEPS TO REPRODUCE 1. Install okular via Microsoft Store or latest stable release from binary Factory 2. Try to add Certificate Database via Settings / Configure Backends / PDF Backends Configuration 3. No Path is shown and can't add manual path because it is grayed out (see picture) 4. Therefore no Available Signatures OBSERVED RESULT Can't add manual path and doesn't find default path EXPECTED RESULT Path is shown and can edit path SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Works fine under Ubuntu 20.04 with Okular Version 21.12.1 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 448258] New: HOME and END key shortcuts are inconsistent
https://bugs.kde.org/show_bug.cgi?id=448258 Bug ID: 448258 Summary: HOME and END key shortcuts are inconsistent Product: okular Version: 21.12.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: andreas.d.k...@gmail.com Target Milestone: --- SUMMARY The shortcuts for "Go to start" and "Go to end" with the HOME/Pos1 and END keys are inconsistent. OBSERVED RESULT (not exhaustive list) Okular & Kate: Go to start: Ctrl + HOME Go to end: Ctrl + END Konsole: Go to start: Shift + HOME Go to end: Shift + END Dolphin/Gwenview/Ark/KSysGuard: Go to start: HOME Go to end: END EXPECTED RESULT For Konsole and Kate it makes sense because HOME goes to the beginning of the line (vice versa for END), which is the more intuitive functionality in these cases. But still, it should be decided for Ctrl or Shift consistently as an auxiliary key if plain Home and End are used otherwise. For Okular I don't see a reason why an auxiliary key is necessary. Otherwise, I'd expect plain HOME and END as the default (usually), and then, if pressed together with an auxiliary key (like Shift or Ctrl), I'd expect some special behavior. As an example for Okular, the proposed functionality from this ticket would feel natural for me with Ctrl + Home/End: https://bugs.kde.org/show_bug.cgi?id=114267 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 447651] Jagged lines (while reviewing pdf) in Freehand drawing from wacom intuos stylus
https://bugs.kde.org/show_bug.cgi?id=447651 --- Comment #4 from yashvp...@gmail.com --- (In reply to David Hurka from comment #1) > We have seen different types of jagging. Can you make a screenshot of a > jagged line at a high zoom value? Added attachments that show one such example at different zoom values. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 447651] Jagged lines (while reviewing pdf) in Freehand drawing from wacom intuos stylus
https://bugs.kde.org/show_bug.cgi?id=447651 --- Comment #3 from yashvp...@gmail.com --- Created attachment 144966 --> https://bugs.kde.org/attachment.cgi?id=144966=edit Example of jagged lines at 800% zoom -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 447651] Jagged lines (while reviewing pdf) in Freehand drawing from wacom intuos stylus
https://bugs.kde.org/show_bug.cgi?id=447651 --- Comment #2 from yashvp...@gmail.com --- Created attachment 144965 --> https://bugs.kde.org/attachment.cgi?id=144965=edit Example of jagged lines while using the stylus -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 447651] New: Jagged lines (while reviewing pdf) in Freehand drawing from wacom intuos stylus
https://bugs.kde.org/show_bug.cgi?id=447651 Bug ID: 447651 Summary: Jagged lines (while reviewing pdf) in Freehand drawing from wacom intuos stylus Product: okular Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: yashvp...@gmail.com Target Milestone: --- SUMMARY Drawing (review->freehand) from the pen results in jagged lines (weird branches created from the main drawing). Okular v 22.03.70 (installed via apt), OS Ubuntu 20.04, Linux (x86_64) release 5.11.0-43-generic. Wacom intuous tablet and stylus. The issue does not occur when using only the mouse, or when annotating (with the stylus) in presentation mode. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE (assuming the same setup as above) 0. Open a pdf in Okular. 1. Goto Tools->Review 2. Click or double-click on Freehand drawing 3. Write/draw anything on the document OBSERVED RESULT Jagged lines with branches growing from the intended drawing when reviewing pdf EXPECTED RESULT Smooth lines SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 20.04 Linux (x86_64) release 5.11.0-43-generic (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 447410] already highlighted text (comments), can not be changed - Additional: right click menu feature request
https://bugs.kde.org/show_bug.cgi?id=447410 --- Comment #2 from phil40...@gmail.com --- >The functionality you need is available if you select the "Browse" tool. OK I see, a bit awkward or at least not natural compared to other apps common behaviour. One needs first to active "browse" mode, before one can right click and get a properties menu of the highlighted text. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 447410] New: already highlighted text (comments), can not be changed - Additional: right click menu feature request
https://bugs.kde.org/show_bug.cgi?id=447410 Bug ID: 447410 Summary: already highlighted text (comments), can not be changed - Additional: right click menu feature request Product: okular Version: 21.12.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: phil40...@gmail.com Target Milestone: --- SUMMARY & STEPS TO REPRODUCE 1. Text highlight in some colour, for instance green, a selection within a pdf. 2. As espected the selection is highligted in the chosen colour. 3. Now suppose you want to change the highligted colour from green to yellow. Try: A/ right clicking(no edit menu) - FEATURE request. B/ or re-select the highlighted text to modify/edit the highlighting colour. It's not possible SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro XFCE -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 174314] regular expression search for okular
https://bugs.kde.org/show_bug.cgi?id=174314 phil40...@gmail.com changed: What|Removed |Added CC||phil40...@gmail.com --- Comment #5 from phil40...@gmail.com --- Not in 21.12.0 @Pino Toscano >Not easy. Why? Not using regexp library/librairies, for instance pdfgrep for pdf's? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 --- Comment #12 from gust...@angulosolido.pt --- Thank you. What would be the versions of Poppler and oKular recommended for an LTS release like 20.04? If the existing ones are so ancient, perhaps some kind of backport can be done. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 --- Comment #9 from gust...@angulosolido.pt --- Hi Albert, I am using the latest from Kubuntu 20.04: * okular 4:19.12.3-2ubuntu1 * poppler-data 0.4.9-2 * libpoppler97:amd64, poppler-utils (and others) 0.86.1-0ubuntu1 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 446298] PDF signature certificate chain validation
https://bugs.kde.org/show_bug.cgi?id=446298 --- Comment #1 from gust...@angulosolido.pt --- Created attachment 144102 --> https://bugs.kde.org/attachment.cgi?id=144102=edit another message panel from Adobe Reader -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 446298] New: PDF signature certificate chain validation
https://bugs.kde.org/show_bug.cgi?id=446298 Bug ID: 446298 Summary: PDF signature certificate chain validation Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: gust...@angulosolido.pt Target Milestone: --- Created attachment 144101 --> https://bugs.kde.org/attachment.cgi?id=144101=edit messages from Adobe Reader I have recently checked that Poppler can provide both: 1. signed PDF content verification (i.e. content was not changed after signature) 2. identify verification, given trusted CA certificates (inserted into the Firefox NSS cert db) Reference: https://gitlab.freedesktop.org/poppler/poppler/-/issues/896#note_1172603 It seems to me that oKular when it says "the signature is cryptographically valid" it refers to 1), which might not be 100% clear to whoever sees that message. Ideally oKular would be able to perform 1 and 2, like Poppler does, and display different messages depending on whether both checks are performed or only the first so that the users understands the level of validation. I am attaching the messages from Adobe Reader to illustrate the idea. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 --- Comment #7 from gust...@angulosolido.pt --- Attached problematic file. It opens correctly on the Firefox builtin PDF viewer and on the GMail PDF preview function. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 --- Comment #6 from gust...@angulosolido.pt --- Created attachment 144099 --> https://bugs.kde.org/attachment.cgi?id=144099=edit how GMail previews the document -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 --- Comment #5 from gust...@angulosolido.pt --- Created attachment 144098 --> https://bugs.kde.org/attachment.cgi?id=144098=edit example file that comes out of Docusign This file can't be opened by oKular. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 gust...@angulosolido.pt changed: What|Removed |Added CC||gust...@angulosolido.pt --- Comment #4 from gust...@angulosolido.pt --- I have exactly the same issue with a PDF coming from Docusign. The PDF renders correctly inside GMail and can be "printed to file from there". Indeed the oKular message does. I will try to obtain a document that can be attached here. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 446194] Selecting background/watermark text instead of foreground/"real" text
https://bugs.kde.org/show_bug.cgi?id=446194 --- Comment #6 from audreys...@pm.me --- It does work on 21.08.3 also on my side ! I was on Ubuntu 20.04. I had to upgrade my Ubuntu to 21.04, and then 21.10. But even then, ubuntu software was only proposing Okular version 20.12.3. Therefore, I downloaded Okular version 21.08.3, using flatpack. https://flathub.org/apps/details/org.kde.okular Thank you ! -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 446237] New: The title bar text is displayed incorrectly
https://bugs.kde.org/show_bug.cgi?id=446237 Bug ID: 446237 Summary: The title bar text is displayed incorrectly Product: okular Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: tenfra...@163.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. The title bar text is displayed incorrectly in Chinese. The first title "File" should be "文件" in Chinese, but it shows "无文字" which means "No text". 2. And the same thing happens to the title "Settings" and "Help". OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 20H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 446194] Selecting background/watermark text instead of foreground/"real" text
https://bugs.kde.org/show_bug.cgi?id=446194 --- Comment #4 from audreys...@pm.me --- (In reply to Albert Astals Cid from comment #3) > Can you confirm the Okular version you're using? Yes, I'm using Okular version 20.12.3 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 446194] Selecting background/watermark text instead of foreground/"real" text
https://bugs.kde.org/show_bug.cgi?id=446194 --- Comment #2 from audreys...@pm.me --- Created attachment 144030 --> https://bugs.kde.org/attachment.cgi?id=144030=edit File with some watermarks -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 446194] New: Selecting background/watermark text instead of foreground/"real" text
https://bugs.kde.org/show_bug.cgi?id=446194 Bug ID: 446194 Summary: Selecting background/watermark text instead of foreground/"real" text Product: okular Version: 20.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: audreys...@pm.me Target Milestone: --- Created attachment 144029 --> https://bugs.kde.org/attachment.cgi?id=144029=edit Select issue okular SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open a text pdf with watermarks 2. Try to select text at the same level of the watermark OBSERVED RESULT Unable to select the real text, okular is selecting on the watermark's base, it's selecting the background text EXPECTED RESULT We would like to select the "real" text, the foreground text, and not the background one. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 20.04.3 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 446184] New: Process 'Print Preview' only for current page and display immediately
https://bugs.kde.org/show_bug.cgi?id=446184 Bug ID: 446184 Summary: Process 'Print Preview' only for current page and display immediately Product: okular Version: unspecified Platform: Flatpak OS: ChromeOS Status: REPORTED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: dalma...@yahoo.com Target Milestone: --- Running Flatpak version Okular 5.15 in Linux subsystem (Debian Buster) of ChromeOS 93. Loading a 98-page magazine in PDF format is pretty quick and looks good in facing-page mode. But... Going to page 50 and clicking on Print Preview, it takes several minutes for the process to display the preview and it starts at page 1. Apparently the preview for the whole document has been prepared. To save time and cpu, it would be better to just compute and display the preview of the current page immediately and continue preparing other pages if I scroll the preview to see them. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445851] Don't copy newlines within paragraph
https://bugs.kde.org/show_bug.cgi?id=445851 --- Comment #2 from codingko...@gmail.com --- Thanks for the response! :) I did have a feeling that there is more going on here than what meets the eye. This would still be convenient to have, but I understand if it's not worth the time to fix those edge cases. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 433003] PDF rendering on dual screen setup with different per-screen scaling appears broken
https://bugs.kde.org/show_bug.cgi?id=433003 pfjarsc...@gmail.com changed: What|Removed |Added CC||pfjarsc...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445868] Okular fills "number only" PDF forms fields with the wrong thousands separator.
https://bugs.kde.org/show_bug.cgi?id=445868 --- Comment #12 from tnem...@free.fr --- (In reply to Albert Astals Cid from comment #11) > Not fixed yet, sorry, needs > https://invent.kde.org/graphics/okular/-/merge_requests/507 to be merged > first :) Anyway, thanks for all. I hope I'll have an updated debian package once the fix is merged ;) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445919] french diacritic characters are not displayed
https://bugs.kde.org/show_bug.cgi?id=445919 sven.zieg...@hotmail.com changed: What|Removed |Added CC|sven.zieg...@hotmail.com| -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445919] french diacritic characters are not displayed
https://bugs.kde.org/show_bug.cgi?id=445919 sven.zieg...@hotmail.com changed: What|Removed |Added CC|yurc...@ukr.net |sven.zieg...@hotmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445868] Okular fills "number only" PDF forms fields with the wrong thousands separator.
https://bugs.kde.org/show_bug.cgi?id=445868 --- Comment #9 from tnem...@free.fr --- (In reply to Albert Astals Cid from comment #8) > ah, right, it's a bunch of javascript executed on focus out. > > I'll try to see if i can figure out what's going on. Thanks :) In the meantime I have a workaround : edit the PDF with LO Draw to remove the comma (and add my signature)... -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445868] Okular fills "number only" PDF forms fields with the wrong thousands separator.
https://bugs.kde.org/show_bug.cgi?id=445868 --- Comment #7 from tnem...@free.fr --- (In reply to Albert Astals Cid from comment #3) > I don't see the problem > https://i.imgur.com/nm61LCW.png Indeed... > Have you modified the default fr_FR.UTF-8 somehow? Never. I'm too old for these kind of games :) As you can see I added screenshots of the several steps I took when entering a value... -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445868] Okular fills "number only" PDF forms fields with the wrong thousands separator.
https://bugs.kde.org/show_bug.cgi?id=445868 --- Comment #6 from tnem...@free.fr --- Created attachment 143832 --> https://bugs.kde.org/attachment.cgi?id=143832=edit closing the form fields Finally when I close the form fields, the value with the wrong thousands separator appears. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445868] Okular fills "number only" PDF forms fields with the wrong thousands separator.
https://bugs.kde.org/show_bug.cgi?id=445868 --- Comment #5 from tnem...@free.fr --- Created attachment 143831 --> https://bugs.kde.org/attachment.cgi?id=143831=edit switching to the next field When I switch to the next field, the comma separator appears even though I did not put it there... -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445868] Okular fills "number only" PDF forms fields with the wrong thousands separator.
https://bugs.kde.org/show_bug.cgi?id=445868 --- Comment #4 from tnem...@free.fr --- Created attachment 143830 --> https://bugs.kde.org/attachment.cgi?id=143830=edit entering the value When the forms field are set to "editable", I enter a value in a number-only field. It's displayed correctly... -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445868] Okular fills "number only" PDF forms fields with the wrong thousands separator.
https://bugs.kde.org/show_bug.cgi?id=445868 --- Comment #2 from tnem...@free.fr --- Created attachment 143825 --> https://bugs.kde.org/attachment.cgi?id=143825=edit PDF with numbers only form fields Numbers only form fields are, for example, in cases B1-6 and B1-8. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445868] New: Okular fills "number only" PDF forms fields with the wrong thousands separator.
https://bugs.kde.org/show_bug.cgi?id=445868 Bug ID: 445868 Summary: Okular fills "number only" PDF forms fields with the wrong thousands separator. Product: okular Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: tnem...@free.fr Target Milestone: --- SUMMARY In my locale (FR) the decimal separator is the comma and the thousands separator is either none or space. In the US, the thousands separator is the comma... When filling my tax information forms, when I want to put 1000, it displays "1,000" which really means "1" locally. STEPS TO REPRODUCE 1. Have a PDF with numbers only form fields and a locale that doesn't have "," as thousands separator 2. Fill the form field with a big enough number 3. Close the form fields and look at the results. OBSERVED RESULT A field with the value "1000" inside displays "1,000". EXPECTED RESULT It should display "1 000". SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 445851] New: Don't copy newlines within paragraph
https://bugs.kde.org/show_bug.cgi?id=445851 Bug ID: 445851 Summary: Don't copy newlines within paragraph Product: okular Version: 21.08.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: codingko...@gmail.com Target Milestone: --- SUMMARY When a selection of text spanning multiple lines is copied, the newlines are included. This has the effect of including newlines in the middle of sentences, which is undesirable when copying text from the PDF to a new document. STEPS TO REPRODUCE 1. Obtain a PDF containing a paragraph of text, such as this one: https://unec.edu.az/application/uploads/2014/12/pdf-sample.pdf. 2. Copy an entire paragraph of text, or a selection within the paragraph spanning multiple times. 3. Paste the selection into a new document or text editor. OBSERVED RESULT Newlines used to break the content are preserved: Adobe® Portable Document Format (PDF) is a universal file format that preserves all of the fonts, formatting, colours and graphics of any source document, regardless of the application and platform used to create it. EXPECTED RESULT Newlines used to break the content are not preserved: Adobe® Portable Document Format (PDF) is a universal file format that preserves all of the fonts, formatting, colours and graphics of any source document, regardless of the application and platform used to create it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The pdf.js PDF viewer elides the newlines as I want, but butchers the spacing in seemingly unrelated ways: Adobe® Portable Document Format (PDF) is a universal file format that preserves allof the fonts, formatting, colours and graphics of any source document, regardless ofthe application and platform used to create it. Bug #359242 also discusses unwanted newlines in the clipboard, but this bug discusses the exclusion of newlines that *are* within the text selection. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 423212] Cannot open Epub files with Chinese in the file name and path
https://bugs.kde.org/show_bug.cgi?id=423212 hremaximil...@outlook.com changed: What|Removed |Added Version|1.10.1 |20.12.2 OS|Other |Microsoft Windows -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 442466] Typewriter and Inline Note text are invisible
https://bugs.kde.org/show_bug.cgi?id=442466 alessiogatto2...@libero.it changed: What|Removed |Added CC||alessiogatto2...@libero.it -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 393869] Markdown backend: Set page format
https://bugs.kde.org/show_bug.cgi?id=393869 k...@yzirkind.com changed: What|Removed |Added CC||k...@yzirkind.com --- Comment #1 from k...@yzirkind.com --- The relevant code is located at https://invent.kde.org/graphics/okular/-/blob/master/core/textdocumentgenerator.cpp#L489-499. Currently only QPrinter::setOutputFormat() is called; QPrinter::setPageSize() needs to be added for this to work. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 442891] When tabs are enabled, opening a document from a file manager in one activity opens the document in a tab on the other activity's Okular, irrespective of whether it is open on th
https://bugs.kde.org/show_bug.cgi?id=442891 mma...@protonmail.com changed: What|Removed |Added CC||mma...@protonmail.com --- Comment #3 from mma...@protonmail.com --- Still occurs in Neon, Plasma 5.23.2, Okular 21.08.2. I would like to add that even if there is an Okular window open on two activities, any new file opened will open in the Okular window most recently opened, regardless of which activity the file was opened from. For example, let's say I opened an Okular window first in Activity 1 and then one in Activity 2. I go back to Activity 1 and try to open a document. This document will open in Activity 2, because that was where the most recent Okular window was opened. Expected result is to have that file open in Activity 1, regardless of which Okular window was most recently opened. Funny thing is that this problem does not exist with separate virtual desktops, despite virtual desktops, to my understanding, being less "separate" than activities in Plasma. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 442975] PDF file annotated with Okular appears corrupted when looked at with other tools
https://bugs.kde.org/show_bug.cgi?id=442975 --- Comment #5 from michael.ko...@gmx.net --- I created a bug report upstream: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1170 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 442975] PDF file annotated with Okular appears corrupted when looked at with other tools
https://bugs.kde.org/show_bug.cgi?id=442975 michael.ko...@gmx.net changed: What|Removed |Added CC||michael.ko...@gmx.net --- Comment #4 from michael.ko...@gmx.net --- I do have an example file which I could share, but the problem appears in Xournal++ for me, not in Okular (I don't use Okular to be honest). Is there already an upstream bug report where I could share the problematic file? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 443928] New: Manga mode
https://bugs.kde.org/show_bug.cgi?id=443928 Bug ID: 443928 Summary: Manga mode Product: okular Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Comicbook backend Assignee: okular-devel@kde.org Reporter: jewas29...@smuvaj.com Target Milestone: --- It would be great when viewing a cbz, if we could reverse the page orders to easily read manga. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 437391] Okular exe from Binary Factory not recognized for default apps on Windows
https://bugs.kde.org/show_bug.cgi?id=437391 --- Comment #1 from gfowl...@outlook.com --- Just adding that is behavior is only with the exe installed from the binary factory. The version installed from the Windows Store does show in the default apps list for PDF files. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 437391] Okular exe from Binary Factory not recognized for default apps on Windows
https://bugs.kde.org/show_bug.cgi?id=437391 gfowl...@outlook.com changed: What|Removed |Added Summary|Okular exe not recognized |Okular exe from Binary |for default apps on Windows |Factory not recognized for ||default apps on Windows -- You are receiving this mail because: You are the assignee for the bug.
