Bug 407173

Summary: Feature request: Hint about logical page numbers in the print dialog
Product: [Applications] okular Reporter: nuntius35 <nuntius35>
Component: printingAssignee: Okular developers <okular-devel>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: nate
Priority: NOR    
Version First Reported In: 1.7.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description nuntius35 2019-05-03 08:05:46 UTC 
SUMMARY
Although the distinction between physical and logical page numbers of a pdf is clearly shown in the bottom of the viewer, many users tend to forget this when they open the print dialog. This causes unnecessary printing.

STEPS TO REPRODUCE
1. Open a pdf document where the physical page numbers are different from the logical page numbers. For example, let's say the document has 30 pages, where pp. i–iii contain the foreword and pp- 1–7, 8–15 and 16–27 contain the first, second and third chapter, respectively
2. Try to print the second chapter: Open the print dialog and enter 8-15 as the page range, press print.
3. Go to the printer.

OBSERVED RESULT
You got pp. 5–12 instead. What a waste of time and paper.

EXPECTED RESULT
I expect that the print dialog displays the same information that I find at the bottom of the viewer. In the example above, the dialog should show something like 5 (8) — 12 (15). I'm not sure which of the fields should be editable, maybe all of them. 

Also, an implementation of https://bugs.kde.org/show_bug.cgi?id=335134 would be really nice.
Comment 1 Nate Graham 2019-05-03 17:46:50 UTC 
> the dialog should show something like 5 (8) — 12 (15)
I feel like that would be really confusing, especially if mixed numbering schemes are added into the mix. If I wanted to print the foreword plus the first chapter, would it say "i. (1) — 7 (10)"?

Another complication: it is presupposed that Okular is able to programmatically understand the document's internal page numbering system, which I don't believe it could possibly do, given the diversity of document types available.

I'm afraid people will just need to remember to print using the viewer app's own page ranges.