Problem description: Steps to reproduce: 1. Pick a cell (let's call it B4) in LibreOffice Calc. Right click->Format Cells...->Alignment->Enable "Shrink to fit cell size" under Properties. (Note with extra detail: The bug is tested to appear when using a wide cell which is merged from columns B to G, where G is the rightmost column of printable area. Use Arial with size 10.) 2. Write long enough text to the cell B4 which wouldn't fit to the cell but would instead overflow with the selected font size 10 (test case had two words which wouldn't fit). 3. Since the "Shrink to fit cell size" is enabled, the text is shown with small enough font size on screen that the text fits in cell. Use print preview or print the page to see the bug. Current behavior: (tested with version 4.3.2) The last words of the text get omitted from the cell when printing, even if they are properly shown in the editing mode. The words which are omitted are ones which wouldn't fit when using the original font size, as if the shrink option would have been forgotten at some point of the code and overflowing words are removed, even if the end result is still using the smaller font size selected by the shrink option. Expected behavior: (worked fine in 4.2.4) Full cell text is printed as expected. -- Note: I have used this feature over many versions, earlier in OpenOffice.org and now later over several versions of LibreOffice. This is broken with this latest version I changed to (4.3.2), but was working fine with the previous one I used (4.2.4).
Created attachment 108996 [details] Screenshot Hi @tonic, thanks for reporting. Reproducible in the screen. Win7x64Ultimate Version: 4.3.3.2 Build ID: 9bb7eadab57b6755b1265afa86e04bf45fbfc644
the error doesn't appear in 4.2.6.2 but in 4.2.7.2
Reproduced -> NEW. Changed severity per the flowchart: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
*** This bug has been marked as a duplicate of bug 82377 ***