Bug 117967

Summary:	Wrong preview choosing two pages per sheet
Product:	[Applications] kdeprint	Reporter:	Iñaki Baz Castillo <ibc>
Component:	general	Assignee:	KDEPrint Devel Mailinglist <kde-print-devel>
Status:	CLOSED DUPLICATE
Severity:	normal	CC:	esigra, jlayt
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Iñaki Baz Castillo 2005-12-09 00:32:12 UTC

Version:           desconocido (using KDE 3.4.2, Debian Package 4:3.4.2-4 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.14

I want to print a document or html with two pages per sheet.
I open print dialog, press on "Properties" and select 2 in "Pages per Sheet".
I select "Preview" and press "Print" so Kghostview appears but only shows one page per sheet (incorrect).
Anyway if I print the document there appear two pages per sheet, but it's extrange to preview the job in a different way.

Now I do exactly the same, but choose "Print to file (pdf)" instead of the printer.
When I press "Print", Kghostview shows two pages per side, exactly like the generated PDF file after I press "Print".

Why I can preview two pages per side when choosing to print to PDF but not when chossing to print in the printer?

Comment 1 Michael Goffioul 2005-12-09 08:59:35 UTC

This (inconsistent) behavior is due to the internal handling of the n-up specification. When, using CUPS and a real printer, this option can be handled by the CUPS server. So the print data are sent to the server without processing the 2-up option and the preview (== print data *before* being sent to the server) shows you 1 page per sheet.
In the case of "Print to PDF", it's not a real CUPS printer, but a kdeprint-specific trick. In that case, the 2-up option is processed by kdeprint itself. So you can directly see the result with 2 pages per sheet.
This bug is probably a duplicated one: I'm sure such a bug report already exists in the DB.

Comment 2 Cristian Tibirna 2005-12-09 12:39:52 UTC


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

Comment 3 John Layt 2008-12-31 19:23:51 UTC

Closing old Resolved status bug.