Bug 142384 - Wrong display text position in file docx
Summary: Wrong display text position in file docx
Status: RESOLVED DUPLICATE of bug 116292
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.3.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: compatibilityMode
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-20 06:52 UTC by amber8706
Modified: 2021-05-20 14:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Test case (93.25 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2021-05-20 06:53 UTC, amber8706
Details
Test compared (111.43 KB, image/png)
2021-05-20 12:25 UTC, Timur
Details
Test saved in MSO 2016 without compatibility (129.35 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2021-05-20 12:26 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description amber8706 2021-05-20 06:52:46 UTC
Description:
Test file attached. MS Office open normaly. Libre - no (wrong text position)

Steps to Reproduce:
1) open attachments file created in MS Office
2) Text "Test" must placed inside black rectangle in each page once.

P.S. This file is exsample without corporative data. The original file is designed in the same way and has the same problems.

Actual Results:
Wrong text position

Expected Results:
Text must placed inside black rectangle in each page once.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Text "Test" must placed inside black rectangle in each page once.
Comment 1 amber8706 2021-05-20 06:53:56 UTC
Created attachment 172182 [details]
Test case
Comment 2 Timur 2021-05-20 12:25:40 UTC
Created attachment 172200 [details]
Test compared

Not so simple..
This is MSO 12 created DOCX. If saved in MSO without compatibility option, it opens differently. 
LO is at least consistent, opens both the same way.
So this is not to be resolved because it's MSO issue.
I'll close the bug. If you can explain why I'm wrong, please set Unconfirmed.
Comment 3 Timur 2021-05-20 12:26:29 UTC
Created attachment 172201 [details]
Test saved in MSO 2016 without compatibility
Comment 4 Timur 2021-05-20 12:32:10 UTC
Hi Justin. Please comment here.
Comment 5 amber8706 2021-05-20 12:55:53 UTC
This file is saved in MSO12. Office 2016 opens it correctly. LibreOffice no. You resave in the 2016 format. Why?! This changes the point of the question. If the file is created in MSO12, then it should open the same way as MSO12 does. (This is what Office 2016 does).
Comment 6 Timur 2021-05-20 13:18:18 UTC
It's the same format DOCX, where MSO changed their behavior in "older" and "newer" versions of OOXML. 
LO conforms to the new behavior, which is good.
You cannot expect of LO to emulate MSO changes and introduce "compatibility" option.
You didn't explain, just repeated what was clear, so I close again.
User can save in MSO without compatibility, reopen and set how it likes, only then bug should be LO's.
Comment 7 amber8706 2021-05-20 13:25:22 UTC
That is, do you think it is normal that the old file formats Office 2016  open normally, but LibreOffice does not?
Comment 8 Justin L 2021-05-20 14:00:55 UTC
There are MANY things at play here. One of the main ones is that the table is a floating table. LibreOffice converts it into a non-floating, non-text-wrapping table because it takes up the full width of the page. That is because LibreOffice is not able to wrap floating tables between pages. [There are plenty of existing bug reports/duplicates about this. See bug 105876.]

So if Amber is trying to make a compatible document, that is one easy way to handle it - just turn wrapping off.

Marking as a duplicate of bug 116292 because that description sounds very similar to what I am seeing. There is a negative vertical positioning value that might be coming into play, pushing it down into the next page. In any case, this is a duplicate of SOMETHING very complicated that LibreOffice simply can't handle.

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