Bug 149370 - FILEOPEN DOCX Content imported without the frame
Summary: FILEOPEN DOCX Content imported without the frame
Status: RESOLVED DUPLICATE of bug 137788
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX-Frames
  Show dependency tree / graph
 
Reported: 2022-05-30 07:56 UTC by Aron Budea
Modified: 2023-03-15 19:29 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Sample DOCX (23.32 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-05-30 07:56 UTC, Aron Budea 		Details
PDF exported from Word (302.88 KB, application/pdf)
2022-05-30 07:57 UTC, Aron Budea 		Details
PDF exported from Writer 7.4 (49.55 KB, application/pdf)
2022-05-30 07:58 UTC, Aron Budea 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2022-05-30 07:56:45 UTC 
Created attachment 180465 [details]
Sample DOCX

The attached document contains a frame with some text and a table within.
When opened in Writer, the content is imported without the frame, and the positioning is incorrect.

Observed using LO 7.4.0.0.alpha1+ (091e615912e123f9d714952b61e2d9b8ae48a043), 3.3.0 / Ubuntu.
Comment 1 Aron Budea 2022-05-30 07:57:07 UTC 
Created attachment 180466 [details]
PDF exported from Word
Comment 2 Aron Budea 2022-05-30 07:58:21 UTC 
Created attachment 180467 [details]
PDF exported from Writer 7.4
Comment 3 Xisco Faulí 2022-05-30 08:56:10 UTC 
Reproduced in

Version: 7.4.0.0.alpha1+ / LibreOffice Community
Build ID: c3baf2a7f48b5ee46c6792b3106cb4fedb4a2ad2
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded
Comment 4 Justin L 2023-03-15 19:29:36 UTC 

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