After upgrading to latest version of libreoffice in mga4, any line changed in calc gets extra vertical padding. For 7ppp or 8ppp font size, it goes from 3.6mm to 4.5mm. There is a noticeably large space above and below each character. This makes it much more difficult to work with large spreadsheets, where vertical space is at a premium. Also, if it is set to the default value, it no longer adjusts the height automatically, for wrap of long lines in a cell, or larger fonts. The previous version (4.1.6.2 ?) did not show such problems.
This is already covered by bug libo#88750 upstream, filed 2015-01-23. Apparently created by a particular kamikaze developer who doesn't think that user opinion matters (from previous conversations). It might be possible to use a macro to fix this bug, but difficult to know before mga#15354 (can't install libreoffice-sdk) is fixed.
Note that upstream it says that an arbitrary minimum row height was introduced to libo calc in version 4.2 This isn't related to the font size. Before this change, if the height of a row wasn't explicitly manually set, the height was automatically determined by the largest font size and the number of lines. There was no minimum row height. Setting the row height manually prevents automatically adding extra vertical height in the event that an entry causes an extra line in the row due to line wrap. It would be nice if a patch could be found to override this change, as despite the protests in libo bugzilla, there is no sign that a correction is coming soon.
Note that there are a few bugs in libo bugzilla relating to this minimal-row-height change. (e.g. 77592 83568 88476)
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD