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 353390 - Fix default rotation angle in portrait print mode
Fix default rotation angle in portrait print mode
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
2.7.x
Other All
: Normal normal
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2006-08-29 12:40 UTC by Michael Chudobiak
Modified: 2006-08-31 18:50 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to correct rotation of landscape-oriented images in portrait print mode (434 bytes, patch)
2006-08-29 12:43 UTC, Michael Chudobiak 		none Details | Review

Description Michael Chudobiak 2006-08-29 12:40:29 UTC 
Please describe the problem:
When a landscape-oriented image is printed in portrait print mode, gthumb automatically rotates it 90 degrees. However, when printed onto punched-hole paper, this places the top of the image opposite the hole side. It is more conventional to place the top of the image next to the hole side. In other words, it would be better if the image were rotated 270 degrees. 

Steps to reproduce:
1. Select a landscape-oriented picture, for instance a photo of a family. 
2. Print onto punched-hole paper, selecting portrait mode in the print dialog.



Actual results:
The family is printed upside-down, if you hold the paper with the holes at the top.

Expected results:
The family is printed right-side up, if you hold the paper with the holes at the top.

Does this happen every time?
Yes.

Other information:
Comment 1 Michael Chudobiak 2006-08-29 12:43:06 UTC 
Created attachment 71827 [details] [review]
Patch to correct rotation of landscape-oriented images in portrait print mode
Comment 2 Michael Chudobiak 2006-08-29 12:44:03 UTC 
I've added a simple one-line patch to fix this.
Comment 3 Paolo Bacchilega 2006-08-31 18:50:22 UTC 
patch applied, thanks.