<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:jluth@mail.com" title="Justin L <jluth@mail.com>"> <span class="fn">Justin L</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Google Doc export to openxml Word docx displays incorrect spacing between image and text box object in Writer and inserts blank pages"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=105134">bug 105134</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;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>DUPLICATE
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Google Doc export to openxml Word docx displays incorrect spacing between image and text box object in Writer and inserts blank pages"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=105134#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Google Doc export to openxml Word docx displays incorrect spacing between image and text box object in Writer and inserts blank pages"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=105134">bug 105134</a>
from <span class="vcard"><a class="email" href="mailto:jluth@mail.com" title="Justin L <jluth@mail.com>"> <span class="fn">Justin L</span></a>
</span></b>
<pre>I think this document was intentionally designed to show off how incapable LO
is of handling continuous breaks.
The first page (which is completely empty) defines a massive top margin. Then
it does NOT do a Section Page-break, but just a continuous break with not
enough space for the next heading/paragraph orphan - which forces it to start
on the second page. How awful of a design is that.
So, there is NO WAY for LibreOffice to know when the new page style should be
applied. It is just "whenever a new page starts", and LO has no corresponding
thing for that.
As a human, it is easy for us to say - well this is a continuous section on the
first paragraph, so we could make it a first/follow pair. But what happens if
the first paragraph is large enough to cover multiple pages? Or what if there
are multiple continuous breaks on the first page? That would break any
"emulation" in the extremer cases. Of course, we could argue to emulate for the
more common cases, so perhaps we could improve some more common documents at
the expense of breaking more extreme examples. (Although I would hate to
classify this document as a common document...)
So, I would say the proper fix for this document is for the author to replace
the continuous section break with a section-pagebreak. (And that is the
solution for pretty much every use of continuous section breaks.)
*** This bug has been marked as a duplicate of <a class="bz_bug_link
bz_status_NEW "
title="NEW - Header, footer and page number missing on second page when saved as docx (continuous section breaks enhancement request)"
href="show_bug.cgi?id=89297">bug 89297</a> ***</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>