Since LibreOffice 4.4.2 (maybe complete 4.4.x line) it is not possible to set a new Calc Document to Zero Margins. Steps to reproduce: - Start new spreadsheet with LibreOffice 4.4.2 - Type in a long (trash) text in A1 which is longer than papersize - set all margins to zero - Look at print preview When you now look at the print preview there is a (white) margin on the right side, instead of no margin. Even the pdf export produces the margin. Old calc documents opened by 4.4.2 which are set to zero margins are working normally. Expected behaviour: Calc respect the margin setting for all documents
I can confirm with Version: 4.5.0.0.alpha0+ Build ID: b024e36ddb3b53163d7a01f6f7b5aadb7a858cd9 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-03-31_09:12:20 and LibreOffice 3.5.0 Build ID: d6cde02 when set margins in dialog - format/page Works OK when I manually move margin slider in preview.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
In LibreOffice 5.0.5 and 5.1.2 the bug still exists.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
In LibreOffice 5.3.3 the bug still exists.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
6.0.4.2 The Bug still exists. To reproduce use steps from first post.
can't repro in Version: 6.2.1.1 Build ID: 757c58e8cb70b2982843211a54750fb3cd79acd5 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded IT, please re-test your bug in LO 6.2
In the current Libreoffice 6.2.0.3 Final the bug still exists.
(In reply to IT from comment #9) > In the current Libreoffice 6.2.0.3 Final the bug still exists. What OS do you use?
Windows 10 (1809) de-DE locale and UI
Dear IT, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Tested with 7.3.6.2 and bug still reproducible
still in 7.6, 24.2 https://ask.libreoffice.org/t/pdf-print-from-calc-always-has-a-blank-right-margin/107238
This was worded from start, that the "new" behavior seen in v.4.4 is different for "new spreadsheets"; while the same v.4.4 behaves "normally" with "old" documents. Yet, there is no such an "old spreadsheet" to see an expected output. I tried to create new documents using the steps from comment 0, using LO 3.4, and also OOo 3.2; and in both, I see the same normal and expected picture, where the whole cells are output to the page, even in the cell overflow situation described in comment 0. That is completely unrelated to margins. A sample "old" document showing the wanted behavior is needed; I guess, that this is NOTABUG / user error, where they simply forgot how they created the old document, e.g. adjusting the cell widths, or maybe using some scaling options in page style.
I'm using Openoffice and later LibreOffice since decades. I changed fast from OO to LO. Sadly actually i can no more remember which old version from OO/LO could be used without this bug. Maybe the originally working document was created by OO 2.x/3.x or LO 3.x. Currently I have no more such old documents. If you are creating a new document (actually tested with LO 24.2.4.2) with the steps mentioned in the first post this bug can be reproduced. In the current state from LO you can not print from calc with zero margin. You get a blank area on the right side.
(In reply to IT from comment #16) This is not correct. You can: just tweak the column width.
Created attachment 194994 [details] A sample that is created anew in v.24.2 Note how I tweaked the width of column I (i.e., a blank column - but it doesn't matter, because it's only important that Calc only prints what fits into whole columns on the page).
Created attachment 194997 [details] Example Price List
Yes I see what you are pointing at. But in real life you often can not rezise the column width. See the example price list. The last word town got cut off with a blank area in page preview. OK the last word cut of because page to small I would think ok. But why is now this blank area? The margin from the page is zero, it should looks like on the left or top, the word cut of at the page limit.
(In reply to IT from comment #20) > OK the last word cut of because page to small I would think ok. But why is > now this blank area? The margin from the page is zero, it should looks like > on the left or top, the word cut of at the page limit. No. As mentioned, spreadsheets are cut at cell boundaries. If there is a pagination, the next page will start where the previous page ends. It can't end or start in the middle of a cell. This is normal and expected behavior. So - the whole question is, what this question is about? 1. If it complains that cells don't break in the middle: this is NOTABUG / WONTFIX. 2. If it's about some behavior changed at some point: this definitely requires the presise description how it worked, so that we could test in an old version and see. 3. If it's about automatic scaling - as available in page style: there the scaling algorithm looks like uses some discrete steps when scalingdown, which usually results in a bit too much scaling, and again, in a whitespace at the right (see e.g. https://ask.libreoffice.org/t/pdf-print-from-calc-always-has-a-blank-right-margin/107238 ) - then this is a reasonable request.
The notabug/wontfix is ok. Sadly i can not test the old LO versions. I've tryed to install 3.3 but it doesn't run on my modern Windows PC. Yeah a better automatic scaling would be great. Here is another quick example: 1. Set all margins to zero (Papersize A4) 2. put test in A1 and I1 3. Align I1 to the right side 4. Set the automatic scaling to fit 1 page Look at the print preview and again you have a blank area on the right side. And on the other hand even without the automatic scaling I would assume that this formatting from steps 1 to 3 alone should produce a print preview over the complete width without any problems. As a user I would assume WYSIWYG. You see the dotted line and the cell margin is set to the right but then the print doesn't reflect this and even the automatic scaling produces this right blank area.
(In reply to IT from comment #22) > Sadly i can not test the old LO versions. I've tryed to install 3.3 but it > doesn't run on my modern Windows PC. What is the error that you see? The old installer first extracts itself into a directory that you can define. Then it checks if a newer version is installed; maybe that is giving the error? I suppose, that you wouldn't want to remove an existing installation just to install version 3.3; the best way would be to simply "unpack" the extracted installer into another directory, where you would get a ready-to-use copy, without a need to install. Just run this command line: msiexec -a path\to\libreoffice33.msi where libreoffice33.msi is inside the directory created by LibO_3.3.0_Win_x86_install_all_lang.exe. On my Windows 11 (without any virtual machines), I can easily run not only LibreOffice 3.3, but even OpenOffice.org 1.0.3 from 2002, and StarOffice 5.2 from 2000. Note that Calc is not WYSIWYG in any mode, even in page break mode. It is focused on "infinite" grid and computations, not on page preview and final printout. It's a spreadsheet program. Possibly there could be a mode designed for WYSIWYG, which would show the same picture you get on page (including margins and header/footer); it would be nice to have, but there's none now.
The install is not the problem, the installed program doesn't start. It complains about missing JRE and then goes into endless loop between splashscreen and missing JRE message and yes this is a problem, because Temurin 21 LTS is not available as 32 bit. We shiftet away from Oracle because of the new java license and all old Oracle JRE got deleted. BTW I tried LO 3.3.4 this was the oldest version I could find. Yeah I know that calc is not WYSIWYG, it's also not a DTP programm, but it is used by many users for this purpose. I can not count how often I see people writing price lists and many other types of documents where I say that is not the type of program to do that. But the table/cell style makes it easy for the user to arrange texts and pictures. And when you try to produce PDF files from that you get crazy if you permanently run into this whitespace print areas. There were some people who mentioned that margin problem to me and back then when I remember correctly with the shift from 3.x to 4.x it got much worse. But there are no documents available from back then. Because of this I reported the bug years ago and sadly I think I can not help anymore to find if this is a regression bug or not. As mentioned also in the link https://ask.libreoffice.org/t/pdf-print-from-calc-always-has-a-blank-right-margin/107238 you can see that this use case for creating PDF file from calc is a thing.
[Automated Action] NeedInfo-To-Unconfirmed