<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - FILEOPEN DOCX TAB_OVER_MARGIN not needed for compatibiltymode >= 15"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=142404#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - FILEOPEN DOCX TAB_OVER_MARGIN not needed for compatibiltymode >= 15"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=142404">bug 142404</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>It looks like this is not just TabOverMargin, but also TabOverflow. Plus
something else which we don't handle yet - the first tab should be full page
width, so that it jumps to a new line if there are any characters before the
tab? [Trading one bad implementation for another?]
It looks like we could set c14 values in SettingsTable::ApplyProperties and
remove TabOverMargin from filter/Writerfilter::setTargetDocument (and set
TabOverflow to false here).
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - "complex" merge example that triggers unbalanced cell start/end tags on docx export"
href="show_bug.cgi?id=90681">tdf90681</a>-1.odt from ooxmlexport5 is one barely-noticable existing unit test
that demonstrates the c15 behaviour. (The footer is two empty lines instead of
one.)</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>