Created attachment 181071 [details] Test document from unit test This is a follow-up to bug 87924. The attached document is the test document from unit test DECLARE_OOXMLIMPORT_TEST(testTdf87924, "tdf87924.docx"). Open the saved document in Word. Notice, that the text appears horizontal. In fact the text is with text direction "Rotate all text 270°" which compensates the 90° shape rotation. Now open the document in LO. The text appears horizontal. Reason is, that the text was set to "Rotate all text 0°". Now save the document without any change to .docx format and open the saved document in Word. Notice, that the text is vertical. The fix for bug 87924 does not really work. But removing the matrix and the rotation test does not solve the problem, since then the text is vertical because the frame does not has the needed rotation for compensation. [The matrix is wrong, but works accidentally for 90° and -90° rotations.] A solution is complicated. I see several ways: A) Keep "Rotate all text 270°" on import and export. But because the attached frame is not able to rotate but honors writing modes, fake the writing direction on rendering, so that it is looks as if the frame could rotate. B) Set "Rotate all text 0°" on import and set it back to "Rotate all text 270°" on export by considering the shape rotation on export too. C) Do not use frames in case the shape is rotated. D) Implement rotation for text frames at least for multiples of 90°. My favorite is to use C) as short term solution. That would solve in addition the error, that the text has a wrong position. Solution D) should be used in the long term. Solution C) would in addition allow to implement a true "upright" in Writer too. Currently the text looks upright because the frame cannot rotate. But saving and opening the saved document in Word shows that "upright" is not handled correctly.
Confirm Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 28daee8a3252e03a67484dc8d3dd26fd73af4826 CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
Dear Regina Henschel, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still not solved in Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a0eb4dcd04a6d8f4a6df474f74edceb8936a3aa6 CPU threads: 32; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded