After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 505448 - print scaling on Evolution not visible on Print Preview
print scaling on Evolution not visible on Print Preview
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Printing
2.17.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-12-24 16:22 UTC by C de-Avillez
Modified: 2018-02-10 03:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description C de-Avillez 2007-12-24 16:22:22 UTC
Original Ubuntu bug: https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/136228

Correct scaling of printer output is, right now, a hit & (mostly) miss operation: since Print Preview does not reflect the scaling selected, the only option for the user to to actually print (or generate PDF output) and check, then try again.

Instead print preview should be called with the selected scaling.
Comment 1 C de-Avillez 2007-12-24 16:28:30 UTC
Also, it would help if the print dialog did not end when selecting "Print Preview". This is bug 479303, but I am unsure if I should set it as a depends here.
Comment 2 Matthew Barnes 2008-03-11 00:37:03 UTC
Bumping version to a stable release.
Comment 3 Matthew Barnes 2009-02-17 03:11:41 UTC
Most of this outside of Evolution's control.  Evolution just draws to whatever Cairo surface it's given.  Recommend retesting and reassigning to GtkPrint if it's still an issue.
Comment 4 Tobias Mueller 2009-09-14 20:22:58 UTC
Hey hggdh :-)

Could you please retest and if this is still an issue reassign to GtkPrint as per comment 3?
Comment 5 C de-Avillez 2009-09-14 21:12:23 UTC
oh boy, how didn't I notice Mattew's comment in February? Ah well.

Reassigning to GTKPrint, and bumping versions to current.
Comment 6 C de-Avillez 2009-10-22 22:48:42 UTC
and, I forgot to state, it is still an issue. Setting back as NEW.
Comment 7 Matthias Clasen 2018-02-10 03:24:49 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.