Bug 310837 - No upscaling when printing an A4-sized PDF file to an A3-sized paper
Summary: No upscaling when printing an A4-sized PDF file to an A3-sized paper
Status: RESOLVED DUPLICATE of bug 322231
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 0.19.60
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-28 17:58 UTC by Jan Kundrát
Modified: 2018-01-17 20:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Kundrát 2012-11-28 17:58:13 UTC
Tried to print the following PDF file:

$ pdfinfo ~/form01.pdf
Author:         [redacted]
Creator:        Draw
Producer:       OpenOffice.org 3.3
CreationDate:   Sun Nov 25 21:25:17 2012
ModDate:        Wed Nov 28 14:29:31 2012
Tagged:         no
Form:           none
Pages:          1
Encrypted:      no
Page size:      595 x 842 pts (A4)
Page rot:       0
File size:      490843 bytes
Optimized:      yes
PDF version:    1.4

via CUPS into "Canon imageRunner C2550 Foomatic/pxlcolor" which is physically capable of printing to A3. I set the File -> Print -> Properties -> Page size in Okular to A3 and the page indeed was printed on an A3-sized paper, but the actual printed size was just an A4-sized region in the middle of the paper.

So I took the original PDF, run `gs -q -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sPAPERSIZE=a3 -dFIXEDMEDIA -dPDFFitPage -sOutputFile=form03.pdf form01.pdf` and the resulting PDF file covers the whole A3 page now.

I would expect that the output shall be either scaled by default, or that there shall be a GUI for making a choice between "print in actual size" and "upscale".

Reproducible: Always
Comment 1 Albert Astals Cid 2014-05-11 13:37:14 UTC
This is a feaure, not a bug
Comment 2 Albert Astals Cid 2014-05-11 13:37:26 UTC
I mean this is a feature request
Comment 3 Michael Weghorn 2018-01-17 16:08:57 UTC
As far as I understand, this is the same as bug 322231 and can therefore be closed as well.
Comment 4 Albert Astals Cid 2018-01-17 20:02:23 UTC

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