Bug 345001 - force printing a4 b5 ... pdf file on a3 pdf sheet
Summary: force printing a4 b5 ... pdf file on a3 pdf sheet
Status: RESOLVED DUPLICATE of bug 322231
Alias: None
Product: okular
Classification: Applications
Component: printing (show other bugs)
Version: 0.21.1
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-10 08:59 UTC by Diego Ercolani
Modified: 2015-03-11 23:29 UTC (History)
1 user (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 Diego Ercolani 2015-03-10 08:59:26 UTC
To the normal use of a document viewer it would be very useful the option to prin very dense sheets on different paper size.
This option isn't working (or better probably is very unintuitive)
as you have to set the output sheet in the print dialog and also in the cups driver. So I think the printing method should be revised to filter out the options unneeded, having some predefined setting will be very useful as in e.g. printing booklet or something like this

Reproducible: Always

Steps to Reproduce:
1. select a pdf file to print
2. try to print on a3 printer
3. watch printed document as a4 sheet centered on a3 sheet
Comment 1 Albert Astals Cid 2015-03-11 22:51:53 UTC
I don't understand which bug you are reporting, please explain what happens and what you would want to happen.
Comment 2 Diego Ercolani 2015-03-11 23:08:36 UTC
Sorry for my fuzzyness
My query is that would be possible from okular to print to a different paper format having okular doing the correction to the ratio.
e.g. printing a source pdf document for example a5 to an a4, having okular correct the aspect ratio to fullfill the a4 paper
Comment 3 Albert Astals Cid 2015-03-11 23:23:07 UTC
So you mean make the printing bigger than it really is?
Comment 4 Diego Ercolani 2015-03-11 23:25:59 UTC
primarly yes
Comment 5 Albert Astals Cid 2015-03-11 23:29:29 UTC

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