1. Open attachment 104763 [details] from bug 82734 2. Save as RTF and reload Observe how "Microsoft Dynamics GP 2013 on Windows Azure" in the footer on the second page is now aligned to the right. I checked in MSO 2013 that left alignment is the correct one. About the history of behaviour: In Linux 43all repo, the range between last36onmaster and last40master seemed promising to bibisect, because in last36onmaster the text position was correct upon opening and then saving to RTF. However, in the range there were commits which produced non-opening RTF files and the repo does not have 1 build per commit, so I did not feel it worth the effort to finish. Starting from 4.0, there was a period where the text was already misaligned upon opening the DOCX. This was fixed by https://git.libreoffice.org/core/commit/7d9bb549d498d6beed2c4050c402d09643febdfa (found in 44max) Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: 09c24681a3414092fde50ec0f617c9f7c79e8a61 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 30 September 2020
I confirm it with Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: threaded
Created attachment 177843 [details] The example file and its RTF version in Writer master Still a problem in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: eb69767d7c1bb8e6e780fd9503f08c9d7f5ecb45 CPU threads: 13; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded Looks like the "Same content on left and right pages" flag is not considered on RTF save. In the DOCX original it is not enabled, but enabling it creates the look seen in RTF. In the RTF version it is enabled.
Dear Buovjaga, 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