[okular] [Bug 383301] New: Feature request: one click selection highlight color, split screen of the same document

https://bugs.kde.org/show_bug.cgi?id=383301 Bug ID: 383301 Summary: Feature request: one click selection highlight color, split screen of the same document Product: okular Version: unspecified Platform: Mint (Ubuntu based)

Re: What should okular background color be

I did this because I wanted to be able to set black as the background color. On 9 Aug. 2017 11:15 am, "Albert Freeman" wrote: > I have added the ability for the background color in okular to be changed > via the settings, but currently what I have done is set the

What should okular background color be

I have added the ability for the background color in okular to be changed via the settings, but currently what I have done is set the default background color to the RGB value of QPalette::Dark since I don't think it is a good idea to construct a QPalette in conf/okular.kcfg just to access

D7212: Don't build kimgiotest unless BUILD_TESTING=ON

This revision was automatically updated to reflect the committed changes. Closed by commit R223:862fd4f3e1d0: Don't build kimgiotest unless BUILD_TESTING=ON (authored by asturmlechner). REPOSITORY R223 Okular CHANGES SINCE LAST UPDATE https://phabricator.kde.org/D7212?vs=17905=17910

D7212: Don't build kimgiotest unless BUILD_TESTING=ON

kfunk accepted this revision. This revision is now accepted and ready to land. REPOSITORY R223 Okular BRANCH Applications/17.08 REVISION DETAIL https://phabricator.kde.org/D7212 To: asturmlechner, #okular, kfunk Cc: kfunk, aacid

D7212: Don't build kimgiotest unless BUILD_TESTING=ON

asturmlechner added a comment. actually ECM git master/KF-5.38 that is, sorry. REPOSITORY R223 Okular REVISION DETAIL https://phabricator.kde.org/D7212 To: asturmlechner, #okular Cc: kfunk, aacid

D7212: Don't build kimgiotest unless BUILD_TESTING=ON

asturmlechner created this revision. Restricted Application added a project: Okular. REVISION SUMMARY In >=KF-5.37 target kimgiotest is only built if BUILD_TESTING=ON, so subsequent target_compile_definitions will fail if OFF. REPOSITORY R223 Okular BRANCH Applications/17.08 REVISION

[okular] [Bug 315552] Allow save annotations directly to original pdf file

https://bugs.kde.org/show_bug.cgi?id=315552 --- Comment #13 from CnZhx --- Thank you, Gregor, for your clarification. It seems I am exactly one of the confused. -- You are receiving this mail because: You are the assignee for the bug.

[okular] [Bug 315552] Allow save annotations directly to original pdf file

https://bugs.kde.org/show_bug.cgi?id=315552 --- Comment #12 from Gregor Mi --- @CnZhx: Normally, Ctrl+S is the "Save" action. So, the usage of Ctrl+S for "Save as..." (which is Ctrl+Shift+S by default) is a non-standard behavior that can confuse users. This will be fixed.

[okular] [Bug 315552] Allow save annotations directly to original pdf file

https://bugs.kde.org/show_bug.cgi?id=315552 --- Comment #11 from CnZhx --- Sorry for the mistake. But I can use Ctrl+s to save the document with annotation as a new pdf file or replace the original one on following environment: ``` openSUSE Tumbleweed: 20170628 KDE Plasma: 5.10.2

[okular] [Bug 315552] Allow save annotations directly to original pdf file

https://bugs.kde.org/show_bug.cgi?id=315552 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment

[okular] [Bug 383274] failure printing via CUPS when document name contains non-ASCII characters

https://bugs.kde.org/show_bug.cgi?id=383274 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org

[okular] [Bug 364809] can't print file that contains invalid UTF-8 sequence

https://bugs.kde.org/show_bug.cgi?id=364809 Albert Astals Cid changed: What|Removed |Added CC||ralf...@gmx.de --- Comment

Re: Review Request 130218: Print via QPrinter when rasterizing and printing annotations

> On Aug. 6, 2017, 3:17 p.m., Albert Astals Cid wrote: > > Rasterizing usually makes stuff look quite bad (because the wrong > > resolution is chosen) , have you tried printing text or things with sharp > > lines? > > Oliver Sander wrote: > Yes I tried that, and it looks very good. It

[okular] [Bug 186677] Better PDF text comments for okular

https://bugs.kde.org/show_bug.cgi?id=186677 CnZhx changed: What|Removed |Added CC||z...@cnzhx.net -- You are receiving

[okular] [Bug 358057] [Usability] Permanent/sticky annotation feature is hard to discover

https://bugs.kde.org/show_bug.cgi?id=358057 CnZhx changed: What|Removed |Added CC||z...@cnzhx.net --- Comment #2 from

[okular] [Bug 315552] Allow save annotations directly to original pdf file

https://bugs.kde.org/show_bug.cgi?id=315552 CnZhx changed: What|Removed |Added CC||z...@cnzhx.net --- Comment #9 from

[okular] [Bug 383139] printing to cups printer silently failing (error on console - lpr: The printer or class does not exist)

https://bugs.kde.org/show_bug.cgi?id=383139 --- Comment #11 from er...@mcalvin.com --- I created a bug for this with openSUSE: https://bugzilla.opensuse.org/show_bug.cgi?id=1052793 -- You are receiving this mail because: You are the assignee for the bug.

[okular] [Bug 383139] printing to cups printer silently failing (error on console - lpr: The printer or class does not exist)

https://bugs.kde.org/show_bug.cgi?id=383139 --- Comment #10 from Yuri Chornoivan --- Just for the reference, the similar bug in Mageia has been fixed by cups-filters patching update. http://advisories.mageia.org/MGAA-2017-0055.html -- You are receiving this mail because: You

[okular] [Bug 383274] New: failure printing via CUPS when document name contains non-ASCII characters

https://bugs.kde.org/show_bug.cgi?id=383274 Bug ID: 383274 Summary: failure printing via CUPS when document name contains non-ASCII characters Product: okular Version: 0.26.1 Platform: openSUSE RPMs OS:

Re: Review Request 130214: Simplify the drawing of buffered highlight rectangles

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/130214/ --- (Updated Aug. 8, 2017, 12:56 p.m.) Status -- This change has been