Version: (using KDE KDE 3.1.3) Installed from: Debian testing/unstable Packages Compiler: gcc 3.3 OS: Linux When I print from KOrganizer (3.1.1 in KDE 3.1.3), sometimes it prints in portrait mode, sometimes it prints in landscape mode. I have no control over which mode it decides to print in - there is no setting for print orientation in the print dialog, and there is no print setup option in the File menu.
Currently KOrganizer does not allow selection of page orientation for printing. Todo and day and printing is alway in portrait, month and timetable printout is always in landscape. An option would be nice, but that's already reported as bug #47764. Thanks for reporting, anyway. Reinhold *** This bug has been marked as a duplicate of 47764 ***
Subject: Re: Can't control whether KOrganizer prints in portrait or landscape mode On Tue 19 Aug 2003 1:35 am, you wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=62916 > reinhold@kainhofer.com changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- Status|UNCONFIRMED |RESOLVED > Resolution| |DUPLICATE > > > > ------- Additional Comments From reinhold@kainhofer.com 2003-08-19 09:35 > ------- Currently KOrganizer does not allow selection of page orientation > for printing. Todo and day and printing is alway in portrait, month and > timetable printout is always in landscape. An option would be nice, but > that's already reported as bug #47764. > > Thanks for reporting, anyway. > > Reinhold > > *** This bug has been marked as a duplicate of 47764 *** That's odd, because I'm getting Todo lists printed in landscape (sometimes.) If Todo lists are always supposed to be in portrait mode, something's wrong. I have Todo lists in both portrait and landscape orientations. Whether it prints portrait or landscape seems completely random. I just fired up KOrganizer, and just got a Day in landscape, and a Month in portrait. Something's definitely wrong. Thanks for replying, Doug