[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 toni_rocha changed: What|Removed |Added CC||antonioni.ro...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462749] New: Menus not functioning. Program is not usable.
https://bugs.kde.org/show_bug.cgi?id=462749 Bug ID: 462749 Summary: Menus not functioning. Program is not usable. Classification: Applications Product: okular Version: 22.08.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: cbarr...@shaw.ca Target Milestone: --- Created attachment 154398 --> https://bugs.kde.org/attachment.cgi?id=154398=edit Menu bug screen shot SUMMARY STEPS TO REPRODUCE 1. Open a pdf document 2. Try to do anything at all. For example, go to view and hit "fit page". Nothing happens. The menu is badly displayed. OBSERVED RESULT Nothing works. Menus look very strange. EXPECTED RESULT I was hoping to add comments to the document. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.1 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Hi. This worked well in the previous LTS version (22.04.04). I have used the program to do a lot of annotations. I have uninstalled it and re-installed it twice. In its current state, I cannot use it at all. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462743] New: Okular markdown backend mismanages UTF-8 encoded chars
https://bugs.kde.org/show_bug.cgi?id=462743 Bug ID: 462743 Summary: Okular markdown backend mismanages UTF-8 encoded chars Classification: Applications Product: okular Version: 22.04.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: markdown backend Assignee: okular-devel@kde.org Reporter: sergio.calleg...@gmail.com Target Milestone: --- SUMMARY Markdown documents with an UTF-8 encoding have non-ascii chars misrendered. STEPS TO REPRODUCE 1. Create a markdown document with some non-ascii chars, using the UTF-8 encoding, for instance insert the char "æ" in the document 2. Open the document with okular 3. See weird chars in place of the UTF-8 encoded non-ascii chars. For instance "æ" renders as "æ" OBSERVED RESULT The markdown backend uses some (hardcoded?) encoding, maybe Latin1. EXPECTED RESULT For documents format where the adopted encoding is not "written inside the document", the okular backend should use the user default encoding as provided by the locale and optionally provide a way to select a different encoding. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are the assignee for the bug.
Re: Blue Angel info | include in manual or "About" info-box?
Hello, On 12/4/22 23:47, Albert Astals Cid wrote: I don't see how to make it fit in the About dialog though. The About dialog is not very customizable (on purpose, so that all apps show the same). One option is to add it as "Other" text, but IMHO it's a bit too prominent, before the copyright and okular webpage link https://i.imgur.com/ZkRIoTr.png The other option is have it in the "Thanks" section, which is semantically wrong (e.g. the web link tooltip says "Visit the contributors page") https://i.imgur.com/VbkajK2.png Maybe we should just go for the manual? I noticed that different applications have different tabs in the Help > About X info box. For instance: Dolphin has "About", "Components, "Authors", while Kate has those plus "Thanks To". Could it be worth adding a "Sustainabaility" / "Eco" tab? This would be a place to include information about Blue Angel eco-certification and other energy measurements, or aspects of the software which make it more sustainable (runs on older hardware, freedom from advertising, etc.)? I think this idea fits well with the sustainability goal, in particular "highlighting where our software is already sustainably designed". https://community.kde.org/Goals/Sustainable_Software What do you think? Cheers, Joseph -- Joseph P. De Veaugh-Geiss BE4FOSS Project and Community Manager (KDE Eco) OpenPGP: 8FC5 4178 DC44 AD55 08E7 DF57 453E 5746 59A6 C06F --- KDE Eco: Building Energy-Efficient Free Software! Website: https://eco.kde.org Mastodon: @be4foss@floss.social Mailing list: https://mail.kde.org/cgi-bin/mailman/listinfo/energy-efficiency Matrix: https://webchat.kde.org/#/room/#energy-efficiency:kde.org Forum: https://forum.kde.org/viewforum.php?f=334
RE: [okular] [Bug 434777] [Snap] Okular does not open in new tab but window
To me, that looks like you are using different okular versions with different settings. Maybe one is snap and one from the system?Von meinem/meiner Galaxy gesendet Ursprüngliche Nachricht Von: bugzilla_nore...@kde.org Datum: 07.12.22 09:50 (GMT+01:00) An: okular-devel@kde.org Betreff: [okular] [Bug 434777] [Snap] Okular does not open in new tab but window https://bugs.kde.org/show_bug.cgi?id=434777--- Comment #3 from giamm...@hotmail.com ---I have just noticed that if a pdf is opened via right click -> open withanother application -> Okular, instead of double-clicking, the file is actuallyopened in a tab of the already opened Okular. How is it possible to code thisas default behaviour?-- You are receiving this mail because:You are the assignee for the bug.
[okular] [Bug 434777] [Snap] Okular does not open in new tab but window
https://bugs.kde.org/show_bug.cgi?id=434777 --- Comment #3 from giamm...@hotmail.com --- I have just noticed that if a pdf is opened via right click -> open with another application -> Okular, instead of double-clicking, the file is actually opened in a tab of the already opened Okular. How is it possible to code this as default behaviour? -- You are receiving this mail because: You are the assignee for the bug.
