Bug 33989 - Print to A3 Page doesn't fit correct
Summary: Print to A3 Page doesn't fit correct
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: x86 (IA32) macOS (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-07 05:01 UTC by khp
Modified: 2012-08-31 10:05 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
test print (19.78 KB, application/pdf)
2011-06-19 10:58 UTC, damm
Details
example file (11.05 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-06-19 11:00 UTC, damm
Details
screenshot (94.02 KB, image/png)
2011-06-19 11:01 UTC, damm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description khp 2011-02-07 05:01:18 UTC
Calc is not able to print a spreadsheet correct to a A3 page format. It doesn't
fit to A3, it is always to big. The Preview on the new Print Page is correct.
But not when I press the Preview Button or print the page, the contents don't
fit to the A3 page format.
This happens with the 'new' printing interface on both OO 3.3 and LO 3.3

I use the following settings:
Page style -> Page-> Papier format-> A3 Landscape
I fit the contents with Page Break Preview for one page
Print with P
Comment 1 damm 2011-06-19 10:58:53 UTC
Created attachment 48164 [details]
test print
Comment 2 damm 2011-06-19 11:00:05 UTC
Created attachment 48165 [details]
example file
Comment 3 damm 2011-06-19 11:01:19 UTC
Created attachment 48166 [details]
screenshot
Comment 4 damm 2011-06-19 11:02:56 UTC
i have the same problem.
LO is printing a A4 landscape instead a A3 landscape.
Comment 5 Björn Michaelsen 2011-12-23 11:46:35 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 6 Florian Reisinger 2012-08-14 13:59:48 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 Florian Reisinger 2012-08-14 14:00:57 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 8 Florian Reisinger 2012-08-14 14:05:41 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 9 Florian Reisinger 2012-08-14 14:07:42 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian