Bug 80155 - FILEOPEN: docx: Horizontally overflowing table.
Summary: FILEOPEN: docx: Horizontally overflowing table.
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.6.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-17 17:34 UTC by NMB
Modified: 2014-06-17 18:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
This is the docx file. It is a simple example case without extra parts. (12.98 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2014-06-17 17:34 UTC, NMB 		Details
This is a pdf of the Word output (what the table should look like.) (168.25 KB, application/pdf)
2014-06-17 17:35 UTC, NMB 		Details
This is the Libreoffice output pdf. It is not correct. (17.20 KB, application/pdf)
2014-06-17 17:36 UTC, NMB 		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 NMB 2014-06-17 17:34:24 UTC 
Created attachment 101256 [details]
This is the docx file. It is a simple example case without extra parts.

Libreoffice Writer does not read the tables in the attached docx file correctly. The table should fit comfortably on one page, but Libreoffice extends it far off to the right.

$ lowriter --version
LibreOffice 4.1.6.2 410m0(Build:2)

              
Operating System: Debian
Version: 4.1.6.2 release
Comment 1 NMB 2014-06-17 17:35:33 UTC 
Created attachment 101257 [details]
This is a pdf of the Word output (what the table should look like.)
Comment 2 NMB 2014-06-17 17:36:24 UTC 
Created attachment 101258 [details]
This is the Libreoffice output pdf. It is not correct.
Comment 3 tommy27 2014-06-17 18:27:37 UTC 
tested under Win7x53 
LibO 4.1.5.2 fails to correctly render that table

LibO 4.2.4.2 shows it like Word

so bug is resolved in current 4.2.x release

I set status RESOLVED WORKSFORME

consider upgrading to 4.2.x since 4.1.x is already end-of-life