Bug 375566

Summary: Okular scale document when printing
Product: [Applications] okular Reporter: fabrice salvaire <fabrice.salvaire>
Component: printingAssignee: Okular developers <okular-devel>
Severity: grave CC: l.allulli, m.weghorn, nate, rdieter, st.gruber
Priority: NOR    
Version: 0.26.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Print pattern

Description fabrice salvaire 2017-01-25 21:59:43 UTC
Okular scale PDF document when printing which means 1 cm is shorter by a factor 96.6 % in my case.

This is a major issue when dimensions must be accurate.

Why printing with okular is not equivalent to the lpr command ?
Comment 1 Rex Dieter 2017-01-26 13:22:20 UTC
can you give a sample document, and mention what paper size(s) you're using (both in document and printer)?
Comment 2 fabrice salvaire 2017-01-26 15:01:06 UTC
Created attachment 103655 [details]
Print pattern
Comment 3 Rex Dieter 2017-01-26 15:06:18 UTC
OK, as far as I can tell, that attached pdf is uses papersize:
8.26772 x 11.6929 in (Portrait A4)

Can we assume the printer uses A4-sized paper too?
Comment 4 fabrice salvaire 2017-01-26 15:27:24 UTC
Document is a4 and I use the "default properties" which are actually set to A4 and margins set to top 4.94, left/right 6.35, bottom 5.29 mm.

I don't understand what is the purpose of theses margins since I want to send the PDF as is to my printer. Does Okular try to fix document with too short margins for a printer? Note acroread provides much advanced scaling printing settings: None, Fit to printable area, Shrink to printable area etc.
Comment 5 fabrice salvaire 2017-01-26 15:29:04 UTC
Yes Cups Printer is set to default: media=iso_a4_210x297mm
Comment 6 Luca Allulli 2017-06-08 07:58:45 UTC
I suggest to add a "Fit to print area" option, like other PDF viewers have (e.g., Foxit and Adobe Reader), because shrinking/scaling should be optional.
Comment 7 Nate Graham 2017-09-29 00:55:27 UTC
Let's mark this as a duplicate of https://bugs.kde.org/show_bug.cgi?id=348172, since once that's fixed, this will be, too.

*** This bug has been marked as a duplicate of bug 348172 ***