[Okular-devel] [okular] [Bug 318999] Ship Service Menu for printing PDF files
https://bugs.kde.org/show_bug.cgi?id=318999 Albert Astals Cid aa...@kde.org changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid aa...@kde.org --- To be honest don't see why we should and say calligra not or kate, etc. If you want a feature like this it should probably be handled at the workspace level, have a daemon with desktop-file-plugins so you can print anything Of course that'll never happen unless someone does the work -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Akademy 2013
El Dijous, 2 de maig de 2013, a les 17:26:22, Mailson Lira va escriure: Hey guys. I'm sending this e-mail to let you know that I'll be attending akademy and also will give a 45min talk about the tiled-based engine (sorry for not telling you before). To be honest i'm quite sad you forgot to tell us, but well, that can hardly be fixed now. Cheers, Albert That's all! ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Akademy 2013
I understand. I was so focused on university stuff lately that I didn't realized how bad it was not telling you guys before. I am really sorry for that. On Mon, May 6, 2013 at 3:12 PM, Albert Astals Cid aa...@kde.org wrote: El Dijous, 2 de maig de 2013, a les 17:26:22, Mailson Lira va escriure: Hey guys. I'm sending this e-mail to let you know that I'll be attending akademy and also will give a 45min talk about the tiled-based engine (sorry for not telling you before). To be honest i'm quite sad you forgot to tell us, but well, that can hardly be fixed now. Cheers, Albert That's all! ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 318998] Add option to exit after printing
https://bugs.kde.org/show_bug.cgi?id=318998 Albert Astals Cid aa...@kde.org changed: What|Removed |Added Keywords||junior-jobs Status|UNCONFIRMED |CONFIRMED CC||aa...@kde.org Ever confirmed|0 |1 --- Comment #1 from Albert Astals Cid aa...@kde.org --- I'd probably go with a --print_and_exit since adding a --exit param makes no sense :D -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 319426] New: Printing text-only PDF files results in empty pages
https://bugs.kde.org/show_bug.cgi?id=319426 Bug ID: 319426 Summary: Printing text-only PDF files results in empty pages Classification: Unclassified Product: okular Version: 0.16.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: sq...@libero.it When printing (with any of my 2 printers) a PDF file containing text, results in a single blank page. If the PDF file has an embedded image in it, that image is printed OK. Reproducible: Always Steps to Reproduce: 1. Create a text files and export it as PDF (i.e. using Open/Libre Office) 2. Open this PDF file with Okular 3. Print it Actual Results: The printer outputs a blank page Expected Results: The printer outputs a correct print. 1. This problem doesn't show when printing from evince document reader (which led me to think it's an okular issue...). 2. CUPS log (set in debug mode) show an error in Ghostscript: googling around led me to these bugs: http://bugs.ghostscript.com/show_bug.cgi?id=691961 - http://bugs.ghostscript.com/show_bug.cgi?id=691985 (both with status RESOLVED WORKSFORME) ; 3. Below, a snippet from CUPS error_log: D [06/May/2013:20:08:19 +0200] [Job 262] GPL Ghostscript 9.05 (2012-02-08) ... D [06/May/2013:20:08:19 +0200] [Job 262] Can't find (or can't open) font file /usr/share/ghostscript/9.05/Resource/Font/NimbusMonL-Regu. D [06/May/2013:20:08:19 +0200] [Job 262] Can't find (or can't open) font file NimbusMonL-Regu. D [06/May/2013:20:08:19 +0200] [Job 262] Can't find (or can't open) font file /usr/share/ghostscript/9.05/Resource/Font/NimbusMonL-Regu. D [06/May/2013:20:08:19 +0200] [Job 262] Can't find (or can't open) font file NimbusMonL-Regu. D [06/May/2013:20:08:19 +0200] [Job 262] Querying operating system for font files... D [06/May/2013:20:08:19 +0200] [Job 262] Can't find (or can't open) font file /usr/share/ghostscript/9.05/Resource/Font/NimbusMonL-Regu. D [06/May/2013:20:08:19 +0200] [Job 262] Can't find (or can't open) font file NimbusMonL-Regu. D [06/May/2013:20:08:19 +0200] [Job 262] Didn't find this font on the system! D [06/May/2013:20:08:19 +0200] [Job 262] Unable to substitute for font. D [06/May/2013:20:08:19 +0200] [Job 262] Error: /invalidfont in /findfont D [06/May/2013:20:08:19 +0200] [Job 262] Operand stack: D [06/May/2013:20:08:19 +0200] [Job 262] F0_99 1 1 --nostringval-- Courier D [06/May/2013:20:08:19 +0200] [Job 262] Execution stack: D [06/May/2013:20:08:19 +0200] [Job 262] %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1878 1 3 %oparray_pop 1877 1 3 %oparray_pop 1861 1 3 %oparray_pop 1755 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- 1836 5 4 %oparray_pop D [06/May/2013:20:08:19 +0200] [Job 262] Dictionary stack: D [06/May/2013:20:08:19 +0200] [Job 262] --dict:1170/1684(ro)(G)-- --dict:0/20(G)-- --dict:84/200(L)-- --dict:67/75(L)-- D [06/May/2013:20:08:19 +0200] [Job 262] Current allocation mode is local D [06/May/2013:20:08:19 +0200] [Job 262] Last OS error: 2 D [06/May/2013:20:08:19 +0200] [Job 262] GPL Ghostscript 9.05: Unrecoverable error, exit code 1 D [06/May/2013:20:08:19 +0200] [Job 262] renderer exited with status 1 D [06/May/2013:20:08:19 +0200] [Job 262] PID 19892 (/usr/libexec/cups/filter/foomatic-rip) did not catch or ignore signal 13. D [06/May/2013:20:08:19 +0200] [Job 262] Possible error on renderer command line or PostScript error. Check options.DEBUG: Sent 0 bytes... D [06/May/2013:20:08:19 +0200] [Job 262] Waiting for read thread to exit... D [06/May/2013:20:08:19 +0200] [Job 262] PID 19893 (/usr/libexec/cups/backend/usb) exited with no errors. D [06/May/2013:20:08:19 +0200] [Job 262] time-at-completed=1367863699 D [06/May/2013:20:08:19 +0200] Discarding unused job-completed event... I [06/May/2013:20:08:19 +0200] [Job 262] Job completed. -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Continuous mode
El Divendres, 3 de maig de 2013, a les 05:26:26, Jaydeep Solanki va escriure: Hi, I would like to know how is continuous mode implemented in Okular.. Can you be a bit more precise? Cheers, Albert Cheers, Jaydeep ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Continuous mode
El Dissabte, 4 de maig de 2013, a les 02:22:39, Jaydeep Solanki va escriure: BTW, why is it that always Albert answers me, no one else o.O ? Because there's not so many Okular developers? I'd expected you to learn about that already :D Cheers, Albert On Fri, May 3, 2013 at 5:26 AM, Jaydeep Solanki jayd...@gmail.com wrote: Hi, I would like to know how is continuous mode implemented in Okular.. Cheers, Jaydeep ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 319442] New: Initial contents of Inline Note annotation discarded
https://bugs.kde.org/show_bug.cgi?id=319442 Bug ID: 319442 Summary: Initial contents of Inline Note annotation discarded Classification: Unclassified Product: okular Version: 0.16.60 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: jon.me...@gmail.com The initial contents of an Inline Note annotation are not preserved when the note 's contents are later edited. Reproducible: Always Steps to Reproduce: 1. Create an inline annotation 2. Enter some initial text in the popup window (The inline note will be created with these contents). 3. Double click the newly created inline note 4. Observe what text the popup annotation window is populated with Actual Results: The popup window's text is empty Expected Results: The popup window should be populated with the initial text entered in step (2) above It looks like the problem is that when the inline note annotation is created the initial text is set using Annotation::setInplaceText (Reference 1), however the annotation popup window is populated using the annotation's contents (Reference 2). When the undo/redo functionality was added the intention was to do away with the distinction between an annotation's contents and inplaceText (See discussion in https://git.reviewboard.kde.org/r/107442/), but this case was not addressed. Proposal: Remove m_inplaceText member from annotationPrivate but remap calls to Annotation::(set)inPlaceText to calls to Annotation::(set)contents for backwards compatibility. While investigating I noticed that the function in Reference 3 should also be cleaned up when this is fixed. References: 1) PickPointEngine::end in pageviewannotator.cpp 2) AnnotWindow::AnnotWindow 3) DocumentPrivate::performSetAnnotationContents in document_p.cpp -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 319442] Initial contents of Inline Note annotation discarded
https://bugs.kde.org/show_bug.cgi?id=319442 Jon Mease jon.me...@gmail.com changed: What|Removed |Added CC||fabiodu...@hotmail.it, ||jon.me...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 319442] Initial contents of Inline Note annotation discarded
https://bugs.kde.org/show_bug.cgi?id=319442 --- Comment #1 from Jon Mease jon.me...@gmail.com --- Fabio, what do you think of the proposal above? -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 319442] Initial contents of Inline Note annotation discarded
https://bugs.kde.org/show_bug.cgi?id=319442 --- Comment #2 from Fabio D'Urso fabiodu...@hotmail.it --- (In reply to comment #0) Proposal: Remove m_inplaceText member from annotationPrivate but remap calls to Annotation::(set)inPlaceText to calls to Annotation::(set)contents for backwards compatibility. Feel free to remove it, there's no one using it apart from ourselves afaik. Haven't read the rest. I'll do it tomorrow (it's night here yawn!) :) -- You are receiving this mail because: You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Continuous mode
On Tue, May 7, 2013 at 3:35 AM, Albert Astals Cid aa...@kde.org wrote: El Divendres, 3 de maig de 2013, a les 05:26:26, Jaydeep Solanki va escriure: Hi, I would like to know how is continuous mode implemented in Okular.. Can you be a bit more precise? Wat I wanted was an overview of how it is implemented. Cheers, Albert Cheers, Jaydeep ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
