Bug 80717

Summary:	FILEOPEN: DOC file has incorrect spacing between tables
Product:	LibreOffice	Reporter:	Marc PHILIPPE <karbock>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	medium	CC:	mst.fdo, philipz85, vmiklos
Version:	4.2.5.2 release	Keywords:	bisected, regression
Hardware:	Other
OS:	Windows (All)
See Also:	https://bugzilla.novell.com/show_bug.cgi?id=863018
Whiteboard:	BSA bibisected interoperability WW8
i915 platform:		i915 features:
Attachments:	Original DOC file, resulting ODT, screenshots

Description Marc PHILIPPE 2014-06-30 15:14:58 UTC

Created attachment 102018 [details]
Original DOC file, resulting ODT, screenshots

Problem description:
When importing the attached DOC file attached, the gap between the 3rd and the 4th row of the table is not respected.
In the original DOC, the gap is 5 mm high.
In the imported ODT, the gap is 5 cm high.

Steps to reproduce:
1. Open the attached DOC.

Current behavior:
The gap is 5 cm high.

Expected behavior:
The gap height should be the same as in the original DOC file.

(Previously commented in bug 80635.)
Operating System: Windows 7
Version: 4.1.5.3 release

Comment 1 Jay Philips 2014-06-30 18:04:40 UTC

Confirmed on Linux Mint in 4.1.6 and 4.3.0. In 4.1, the space between tables shrinks, while in 4.2 and above it expands. The second table is in the correct position in 4.0.6, but the first table isnt present.

This issue maybe the byproduct of the tables going over the page width mentioned in bug 80635.

Comment 2 Michael Stahl 2014-07-10 22:08:45 UTC

the spacing is tiny since the de-floating of the table with
commit 8fe8bd6c3b5b1a539b7370f8c457fa69c061d2de

the 5 cm gap comes from:

commit 9d981abc3f310adf9af3454dd515ea356b31d3c1
Author:     Miklos Vajna <vmiklos@collabora.co.uk>
AuthorDate: Mon May 26 12:04:39 2014 +0200

    bnc#863018 WW8 import: fix upper margin of multi-page floating table

Comment 3 Björn Michaelsen 2014-10-16 14:59:05 UTC

(This is an automated message.)

It seems that the commit that caused this regression was identified. (Or at least a commit is suspected as the offending one.)

Thus setting keyword "bisected".

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.