<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:baron@caesar.elte.hu" title="Aron Budea <baron@caesar.elte.hu>"> <span class="fn">Aron Budea</span></a>
</span> changed
<a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - FILEOPEN Multiple sections with different margins change 2-column layout to 4 in DOC"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=120145">bug 120145</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Keywords</td>
<td>bibisectRequest
</td>
<td>bibisected, bisected
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - FILEOPEN Multiple sections with different margins change 2-column layout to 4 in DOC"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=120145#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - FILEOPEN Multiple sections with different margins change 2-column layout to 4 in DOC"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=120145">bug 120145</a>
from <span class="vcard"><a class="email" href="mailto:baron@caesar.elte.hu" title="Aron Budea <baron@caesar.elte.hu>"> <span class="fn">Aron Budea</span></a>
</span></b>
<pre>Bibisected to the following commit using repo bibisect-44max. Might be
difficult to fix.
author Luboš Luňák <<a href="mailto:l.lunak@collabora.com">l.lunak@collabora.com</a>> 2014-07-21 10:56:52
+0200
committer Luboš Luňák <<a href="mailto:l.lunak@collabora.com">l.lunak@collabora.com</a>> 2014-07-21 11:02:04
+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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>