Bug 109138 - FILEOPEN: table and chart in the imported word documents are misplaced
Summary: FILEOPEN: table and chart in the imported word documents are misplaced
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Tables-Select
  Show dependency treegraph
 
Reported: 2017-07-15 20:21 UTC by Jozef Riha
Modified: 2018-08-07 21:30 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
test document (59.50 KB, application/msword)
2017-07-15 20:21 UTC, Jozef Riha
Details
screenshot of a document as rendered by ms word 2007 (28.07 KB, image/png)
2017-07-15 20:23 UTC, Jozef Riha
Details
screenshot of a document as rendered by libreoffice (42.96 KB, image/png)
2017-07-15 20:24 UTC, Jozef Riha
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jozef Riha 2017-07-15 20:21:19 UTC
Created attachment 134652 [details]
test document

open attached document in ms word and libreoffice and compare side by side. observe positions of both table and column chart. rendering in LO appears to be broken.
Comment 1 Jozef Riha 2017-07-15 20:23:52 UTC
Created attachment 134653 [details]
screenshot of a document as rendered by ms word 2007
Comment 2 Jozef Riha 2017-07-15 20:24:19 UTC
Created attachment 134654 [details]
screenshot of a document as rendered by libreoffice
Comment 3 Xisco Faulí 2017-07-17 09:08:11 UTC
Confirmed in

Version: 6.0.0.0.alpha0+
Build ID: 08f6f9dded1b142b858c455da03319abac691655
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group


- Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e


- LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 4 QA Administrators 2018-07-26 02:42:00 UTC Comment hidden (obsolete)
Comment 5 Jozef Riha 2018-08-07 21:30:18 UTC
seems to be fixed in 6.0.5.2