Created attachment 144186 [details]
Example file from Excel
In Excel, if there is more text in a cell than what it can display, the beginning of the text is displayed and the end of it is hidden.
In Calc, if there is more text than what can fit, all of the text is displayed with the beginning and end outflowing to neighboring cells.
This can easily result in unreadable cells containing the end of the text in the previous cell and the beginning of the text in the next one as well.
Tested with bibisect-win32-6.2
Build ID: ea59fc4831b9d2430de51faa8c3e0a24e6d90cd1
CPU threads: 4; OS: Windows 6.3; UI render: default;
Locale: hu-HU (hu_HU); Calc: CL
Created attachment 144187 [details]
Screenshot of the file in Excel and Calc side by side
Created attachment 144188 [details]
The same file saved as ODS - no change
Worth noting that this happens with 90 degrees rotated text.
Created attachment 144189 [details]
The original file with more unrotated text than cells can display
Created attachment 144190 [details]
The example file with unrotated contents
In case of unrotated text the center part of the text is displayed, but the beginning and end is not overflowing into neighboring cells.
Build ID: 1af7f19224f18e5025352339648db659575eae33
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); Calc: threaded
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.10; Render: default;
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
@Eike, I thought you could be interested in this issue...
Dear Gabor Kelemen,
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!
Still present in
Version: 220.127.116.11.alpha1+ (x86)
Build ID: 80109586e6cb6d3e2e0a53a9079c3125ec9b8368
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win;
Locale: hu-HU (hu_HU); UI-Language: en-US