Bug 123326 - FILEOPEN | DOCX, Rectangle width changes when opened in LO.
Summary: FILEOPEN | DOCX, Rectangle width changes when opened in LO.
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: implementationError
Depends on:
Blocks: OOXML-Shapes
  Show dependency treegraph
 
Reported: 2019-02-11 09:27 UTC by NISZ LibreOffice Team
Modified: 2022-12-20 13:09 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
The original file (57.84 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-02-11 09:27 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word and Writer. (404.89 KB, image/png)
2019-02-11 09:27 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2019-02-11 09:27:06 UTC
Description:
Opening the attached file in LO changes the rectangle’s width in docx.

Steps to Reproduce:
    1. Open the attached file in LO and MSO.
    2. Compare the rectangles.

Actual Results:
The rectangles in LO have a bigger width than in MSO.

Expected Results:
Expected results: The rectangles width should stay the same even in LO.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 NISZ LibreOffice Team 2019-02-11 09:27:40 UTC
Created attachment 149090 [details]
The original file
Comment 2 NISZ LibreOffice Team 2019-02-11 09:27:56 UTC
Created attachment 149091 [details]
Screenshot of the original document side by side in Word and Writer.
Comment 3 Dieter 2019-02-12 08:17:38 UTC
I confirm it with

Version: 6.3.0.0.alpha0+ (x64)
Build ID: f42554a1886ebe49170c25096dc3281b2c7bb1f4
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-02-08_22:37:30
Locale: en-US (de_DE); UI-Language: en-US
Calc: threaded

and with

Version: 5.4.7.2 (x64)
Build-ID: c838ef25c16710f8838b1faec480ebba495259d0
CPU-Threads: 4; BS: Windows 6.19; UI-Render: GL; 
Gebietsschema: de-DE (de_DE); Calc: CL

in comparison to MW Word 2016
Comment 4 NISZ LibreOffice Team 2020-09-03 10:09:53 UTC
I see a similar problem here as in bug #80526
"Word wrap text in shape" is not checked in Word but is checked in Writer for those shapes that become wider. Checking these in Word results in similar shape width as in Writer. Probably a duplicate.

There is also a top - down arrow that is vertical in Word but horizontal in Writer that's probably bug #122717
Comment 5 Timur 2021-02-26 13:38:49 UTC
Not sure if the same, but let me keep it here so far: DOCX attachment 114591 [details] from bug 90442 that looks like attachment 170085 [details] (properties are for a line and not relevant here). 
LO's shapes have textboxes that are too small, so the labels wrap. 
(I write for line shape positions separately).
Comment 6 NISZ LibreOffice Team 2021-04-15 09:52:07 UTC
(In reply to Timur from comment #5)
> Not sure if the same, but let me keep it here so far: DOCX attachment 114591 [details]
> [details] from bug 90442 that looks like attachment 170085 [details]
> (properties are for a line and not relevant here). 
> LO's shapes have textboxes that are too small, so the labels wrap. 

Yes that's the same problem as here. The Provider, Internet, Client 1 and Client 2 boxes in Word have the "Word wrap text in shape" property turned off in Word.

In bug #80526 we solved the correct import of this setting, but then realized this function is not working correctly for the Writer textframe (if you were to set it manually in the Format - Text box and Shape - Text dialog), which was solved in bug 137803.

Now: if you select one of these boxes and open the Format - Text box and Shape - Text dialog, then close it, their size is corrected and they become single line. 
Same goes for the attachment 149090 [details] in comment #1

So applying the setting at import time is still left to fix, I'd hope in this bug.

And of course exporting the setting to docx is still not happening - see bug 136881 about that.