Created attachment 160841 [details] Screenshot of the original document side by side in Word and Writer Attachment #147413 [details] (from bug #92444) looked good in 6.4 but started to regress in 6.5 master with the last 4 text boxes slipping into each other. Steps to reproduce: 1. Open attachment #147413 [details] Bibisected using bibisect-win64-6.5 to: URL: https://cgit.freedesktop.org/libreoffice/core/commit/?id=249428202be04ab9a2271a9cd48922523fa03bc4 author Miklos Vajna <vmiklos@collabora.com> 2020-04-20 21:04:30 +0200 committer Miklos Vajna <vmiklos@collabora.com> 2020-04-21 09:17:07 +0200 tdf#131446 DOCX import: restrict IncreasedAnchoredObjectSpacing further
It would make sense to mention what Word version you use for the reference screenshot. The IncreasedAnchoredObjectSpacing code in writerfilter/ is a hack to stay compatible with that is a Word layout bug, even confirmed by Microsoft. Very rare case. Restricting that hack to the bare minimum, just to affected documents is great idea. That above commit goes in that direction, so I would be hesitant to undo it. See core.git commit 8b73bafbc18acb4dd8911d2f2de8158d98eb6144 for a test file where that workaround is needed. If this bugdoc is rendered the "good" way in Word 2010 as well, then it's a different problem and the above commit just uncovered a pre-existing problem. Hope this helps. :-)
Split from bug 92444
Created attachment 160852 [details] Screenshot of tdf115719.docx in Word 2013 and current master Writer I'm on 2013 Word and the tdf115719.docx example files shapes also slip into each other with current master, and since the same commit.
Ah, interesting. :-) I'm on core.git a2ff84ba180a7533ddd02e776a299522c60ec968 (i.e. master as of yesterday) and get 2 pages for sw/qa/extras/ooxmlexport/data/tdf115719.docx. sw/qa/extras/ooxmlexport/ooxmlexport11.cxx:320 also asserts the page number. I wonder why you get 1 page instead. Any local changes? Does the mentioned test pass for you?
Version: 6.3.5.2 is good looking Build ID: dd0751754f11728f69b42ee2af66670068624673 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US Calc: threaded On Version: 6.4.4.1 is bad looking Build ID: b50bc319eca5cd5b66fbfe2ebd0d3bd1eed099b5 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US Calc: threaded On Version: 7.0.0.0.alpha1 is bad looking Build ID: 6a03b2a54143a9bc0c6d4c7f1... CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded On Version: 7.0.0.0.alpha1+ is bad looking Build ID: b1e396d86655a0131498a4691dd8069ea76c3477 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-05-15_04:58:38 Calc: threaded
Version: 6.4.2.2 good looking Build ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US Calc: threaded Version: 6.4.3.2 good looking Build ID: libreoffice-6.4.3.2-snap1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US Calc: threaded
(In reply to Miklos Vajna from comment #4) > Ah, interesting. :-) I'm on core.git > a2ff84ba180a7533ddd02e776a299522c60ec968 (i.e. master as of yesterday) and > get 2 pages for sw/qa/extras/ooxmlexport/data/tdf115719.docx. > sw/qa/extras/ooxmlexport/ooxmlexport11.cxx:320 also asserts the page number. > I wonder why you get 1 page instead. Any local changes? Does the mentioned > test pass for you? No local changes, I use TB77 nightly build (updated today) on Win8.1: Version: 7.0.0.0.alpha1+ (x64) Build ID: 557c6777ad33b54af28541a96bcf91596995b388 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: hu-HU (hu_HU); UI: en-US Calc: CL
Created attachment 165520 [details] DOCX resaved in MSO - compared (In reply to Miklos Vajna from comment #1) > See core.git commit 8b73bafbc18acb4dd8911d2f2de8158d98eb6144 for a test file > where that workaround is needed. If this bugdoc is rendered the "good" way > in Word 2010 as well, then it's a different problem and the above commit > just uncovered a pre-existing problem. Hope this helps. :-) Yes, this DOCX resaved in MSO 2016 is rendered the "good" way in Word 2010.
Dear NISZ LibreOffice Team, 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
92444 drugs leaflet MSO.docx is very likely a duplicate of bug 95623. *** This bug has been marked as a duplicate of bug 95623 ***