Created attachment 143742 [details] Word doc with table in text box Have some old Word doc templates with basic text boxes with a simple table in them, where Writer messes up the formatting and moves the table to a separate page Example attached
Tested 6.0 - 6.0.6RC as well as 6.1RC on Windows, 32 and 64 bit.
Hi Rodney, thank you for reporting the bug. Can you add a PDF that shows the correct layout?
I can confirm with Version: 6.2.0.0.alpha0+ Build ID: ea59fc4831b9d2430de51faa8c3e0a24e6d90cd1 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; regression, in 4.1 it's not exactly the same as in word, but table is inside the textbox.
Created attachment 144121 [details] printscreen from word2010
Created attachment 144214 [details] bibisect in 44max repo, tail of terminal output Working on debian-buster in 44max bibisect repository, I see that the bug entered LibreOffice in source-hash-c5ed52b1cd6f22787c94bec035ceecf9e1da3271 commit c5ed52b1cd6f22787c94bec035ceecf9e1da3271 Author: Luboš Luňák <l.lunak@collabora.com> AuthorDate: Mon Jul 21 10:56:52 2014 +0200 Commit: Luboš Luňák <l.lunak@collabora.com> CommitDate: Mon Jul 21 11:02:04 2014 +0200 ww8import create a pagedesc if continuous section changes margins (bnc#875383) This is similar to what writerfilter does. MSWord can have one page with several different margins, which are saved using continuous sections, which causes all kinds of trouble, because either we treat them as Writer sections, which means we lose some of the data, or we treat them as Writer page styles, which causes spurious page breaks if in the wrong place. Either option has its problems, but here it seems slightly better to go for keeping the data and hoping the page break will be in a place where a break will be anyway. Change-Id: I8f52aa820750da6788ea04180a15ac334f6bf87b I was able to get a stable result from bibisect only by creating a new user profile at each step. I would welcome thoughts about why this might be necessary. Seeing "either option has its problems" in the log message, I wonder if this bug is one we can fix. I am setting keywords bibisected, bisected.
(In reply to Terrence Enger from comment #5) > I was able to get a stable result from bibisect only by creating a new > user profile at each step. I would welcome thoughts about why this > might be necessary. Happens sometimes, perhaps some compat option was added that had an impact on it.
I tested with 6.2beta1 and see this bug is still here. Is this something that can get hammered out? Anything else you need me to test or provide?
cc: Lubos Lunak, because of bibisect result in comment 5
Closing as a dupe of bug 87764 *** This bug has been marked as a duplicate of bug 87764 ***