<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 WONTFIX - FILEOPEN DOC: tabstops with numbering is generally wrong - many scenarios"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=135201">bug 135201</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>UNCONFIRMED
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - FILEOPEN DOC: tabstops with numbering is generally wrong - many scenarios"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=135201#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - FILEOPEN DOC: tabstops with numbering is generally wrong - many scenarios"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=135201">bug 135201</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>(In reply to Justin L from <a href="show_bug.cgi?id=135201#c0">comment #0</a>)
<span class="quote">> MS Word ignores IndentAt if there are any tabstops specified.
> Writer stops at IndentAt regardless of tabstops (usually).</span >
Word ignores IndentAt if the style OR the paragraph defines a tabstop.
Writer ignores IndentAt only if the NUMBERING STYLE itself defines the tabstop.
The huge problem here is the mixture of style context and paragraph context.
The style CANNOT modify its tabstop, because the same style can exist in
combination with many different paragraph scenarios. So a lousy approach would
be to copy the numbering properties onto each paragraph - which is incredibly
annoying and problematic when editing later on.
But the only other option that I can think of for maintaining compatibility
would be to add a layout compatibility flag which acts like Word - which would
be a huge, complicated task I'm sure.
The last option is just to ignore these import incompatibilities, and force the
user to design a more interoperable document - which is possible, but not
necessarily intuitive. I think that is the best option.
For export, this was solved (for most cases) with <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - FILESAVE DOC: tabstop after bullet point in wrong position for MSWord (comment 9)"
href="show_bug.cgi?id=59674">bug 59674</a> by changing
ineffective numbering-style tabstops to be set at IndentAt instead.
<span class="quote">> MS Word stops at a default tabstop if it is before IndentAt.
> Writer ignores default tabstops - jumping to IndentAt.</span >
For export, this hasn't been a problem, since apparently paragraph tabstops are
defined, and so default tabstops never apply.
For import, this could be emulated by explicitly setting all possible default
tabstops on the paragraph. That should not be dangerous because the tabstops
exist already - just that they are default. So it just means littering
paragraphs with tabstop information. That's lousy, but a fairly common solution
for numbering-related things.
This situation is not commonly seen, since Word adds the style's tabstop to the
paragraph itself when numbering is applied, so the case where default tabstops
come into play is unusual.
So, I think I'll mark this as WONTFIX. The effort is not worth it, the side
effects are annoying, and the likelihood of these situations happening is
small.</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>