Bug 365161

Summary: Can't select which pages to print
Product: [Applications] okular Reporter: Jeffrey <eljefedelito>
Component: printingAssignee: Okular developers <okular-devel>
Status: RESOLVED UPSTREAM    
Severity: normal CC: jean-marie.chosson2, m.weghorn, nate, oliver.sander
Priority: NOR    
Version First Reported In: 0.25.0   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jeffrey 2016-07-06 17:01:37 UTC 
Hello, I have a 49 page PDF that I want to print into a booklet, 2 pages per side on double-sided paper.  I have determined that the layout should print the pages in this order (with some duplicates for filler space):

1,1,2,1,1,3,4,49,48,5,6,47,46,7,8,45,44,9,10,43,42,11,12,41,40,13,14,39,38,15,16,37,36,17,18,35,34,19,20,33,32,21,22,31,30,23,24,29,28,24,25,27,26

However, Okular doesn't allow me to type in print ranges or selected pages or the print order.  This seems like a usability issue that would be a great option to have.

Reproducible: Always

Steps to Reproduce:
1. Open large PDF
2. Try to print specific pages
3. Fail

Actual Results:  
Can't print the ranges and order that I want

Expected Results:  
I think it should give the option to print specific pages as defined in the dialog

This may go beyond Okular, not entirely sure; reassign if needed.  Thanks for KDE and Okular!
Comment 1 JMarieChosson 2017-05-14 12:55:56 UTC 
Hello,

I'm also searching such function in Okular !
Without it, even if okular is now my new viewer by default, i often re-use evince to make "aux p'tits oignons" printing !
This function is already able to be used with EVINCE or LibreOffice, and is very convenient !

Thanks for this very good tool : okular !
And sorry for my bad use of english...

Kore

JMarie
Comment 2 Oliver Sander 2017-05-15 12:28:38 UTC 
As I understand it this not Okular's fault.  Okular uses the standard Qt print dialog, and that one is missing the required feature.
Comment 3 Nate Graham 2017-09-13 02:47:45 UTC 
Yeah, and the Qt bug is https://bugreports.qt.io/browse/QTBUG-1311.