Bug 96219 - FILEOPEN: MSO DOCX image incorrectly placed when using Top Margin Position
Summary: FILEOPEN: MSO DOCX image incorrectly placed when using Top Margin Position
Status: RESOLVED DUPLICATE of bug 113946
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.5.0.0.alpha0+ Master
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks:
 
Reported: 2015-12-03 04:47 UTC by Luke
Modified: 2018-01-22 07:22 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Example of image placed using Word's relative to "Top Margin" (45.19 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2015-12-03 04:47 UTC, Luke
Details
Same file saved as .DOC, correctly imported. (59.50 KB, application/msword)
2015-12-03 04:49 UTC, Luke
Details
printscreens (306.88 KB, application/vnd.oasis.opendocument.text)
2015-12-13 08:42 UTC, raal
Details
Screenshot showing the issue (214.24 KB, image/png)
2016-12-21 06:55 UTC, Luke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luke 2015-12-03 04:47:43 UTC
Created attachment 120973 [details]
Example of image placed using Word's relative to "Top Margin"

The DOCX importer incorrectly maps Word's "Top Margin" to "Margin". The MS-DOC importer correctly maps it to "Entire Page". This is exacerbated by Bug 96218 shifting it further down.
Comment 1 Luke 2015-12-03 04:49:43 UTC
Created attachment 120974 [details]
Same file saved as .DOC, correctly imported.

Note how the format image->type->vertical position settings differ from the .DOCX version.
Comment 2 Buovjaga 2015-12-05 16:59:19 UTC
Confirmed.

OK in 4.3.

Win 7 Pro 64-bit, Version: 5.0.3.2 (x64)
Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75
Locale: fi-FI (fi_FI)

Version: 5.2.0.0.alpha0+
Build ID: 81fa5340191baf8687f9c82f1f414f5afc86b529
Threads 4; Ver: Windows 6.1; Render: default; 
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-03_21:19:19
Locale: fi-FI (fi_FI)

4.3.0.1
Comment 3 raal 2015-12-07 12:01:13 UTC Comment hidden (obsolete)
Comment 4 Joel Madero 2015-12-13 06:24:35 UTC Comment hidden (obsolete)
Comment 5 raal 2015-12-13 08:41:29 UTC Comment hidden (obsolete)
Comment 6 raal 2015-12-13 08:42:30 UTC Comment hidden (obsolete)
Comment 7 Xisco Faulí 2016-11-16 23:21:33 UTC Comment hidden (obsolete)
Comment 8 Luke 2016-12-21 06:46:03 UTC
I guess my description and title were not clear enough. This is NOT a regression. 

The DOCX importer incorrectly maps Word's "Top Margin" to "Margin". The MS-DOC importer correctly maps it to "Entire Page". This is not about the regression, bug 96218, that's a separate issue which is why I filed a separate report.
Comment 9 Luke 2016-12-21 06:55:35 UTC
Created attachment 129836 [details]
Screenshot showing the issue

Hopefully this picture will clear up the confusion.
Comment 10 QA Administrators 2017-12-22 03:36:18 UTC Comment hidden (obsolete)
Comment 11 Luke 2017-12-27 05:04:35 UTC
Still reproducible with Version: 6.1.0.0.alpha0+ (x64)
Build ID: bf8e8cf11bc0d60ab80f5b3420dc424aec2fa626

The DOCX importer is still incorrectly mapping the positing to "Margin" instead of "Entire Page".
Comment 12 Patrick Jaap 2018-01-22 06:44:19 UTC
Hi, this issue is fixed in current master,

see https://bugs.documentfoundation.org/show_bug.cgi?id=113946

Regards,
Patrick
Comment 13 Luke 2018-01-22 07:22:42 UTC

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