Bug 133054 - FILEOPEN DOCX Text boxes slip into each other
Summary: FILEOPEN DOCX Text boxes slip into each other
Status: RESOLVED DUPLICATE of bug 95623
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected
Depends on:
Blocks: DOCX-Textbox
  Show dependency treegraph
 
Reported: 2020-05-15 07:23 UTC by NISZ LibreOffice Team
Modified: 2023-06-03 22:56 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of the original document side by side in Word and Writer (435.20 KB, image/png)
2020-05-15 07:23 UTC, NISZ LibreOffice Team
Details
Screenshot of tdf115719.docx in Word 2013 and current master Writer (74.62 KB, image/png)
2020-05-15 11:52 UTC, NISZ LibreOffice Team
Details
DOCX resaved in MSO - compared (407.26 KB, image/png)
2020-09-15 12:36 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2020-05-15 07:23:59 UTC
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
Comment 1 Miklos Vajna 2020-05-15 07:34:28 UTC
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. :-)
Comment 2 Buovjaga 2020-05-15 07:47:00 UTC Comment hidden (obsolete)
Comment 3 NISZ LibreOffice Team 2020-05-15 11:52:16 UTC
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.
Comment 4 Miklos Vajna 2020-05-15 12:29:11 UTC
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?
Comment 5 BogdanB 2020-05-15 20:33:37 UTC
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
Comment 6 BogdanB 2020-05-15 20:40:09 UTC Comment hidden (obsolete)
Comment 7 NISZ LibreOffice Team 2020-05-18 13:39:27 UTC
(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
Comment 8 Timur 2020-09-15 12:36:51 UTC
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.
Comment 9 QA Administrators 2022-10-28 03:32:32 UTC Comment hidden (obsolete, spam)
Comment 10 Justin L 2023-06-03 22:56:20 UTC
92444 drugs leaflet MSO.docx is very likely a duplicate of bug 95623.

*** This bug has been marked as a duplicate of bug 95623 ***