<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:roland@logikalsolutions.com" title="roland@logikalsolutions.com">roland@logikalsolutions.com</a>
</span> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - FORMATTING: Docx file looks good on screen and prints but fails to reload"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138694">bug 138694</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;">Resolution</td>
<td>INSUFFICIENTDATA
</td>
<td>---
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>RESOLVED
</td>
<td>REOPENED
</td>
</tr>
<tr>
<td style="text-align:right;">Ever confirmed</td>
<td>
</td>
<td>1
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - FORMATTING: Docx file looks good on screen and prints but fails to reload"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138694#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - FORMATTING: Docx file looks good on screen and prints but fails to reload"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138694">bug 138694</a>
from <span class="vcard"><a class="email" href="mailto:roland@logikalsolutions.com" title="roland@logikalsolutions.com">roland@logikalsolutions.com</a>
</span></b>
<pre>(In reply to Justin L from <a href="show_bug.cgi?id=138694#c10">comment #10</a>)
<span class="quote">> I can't think of anything that we could do about this bug report.
> 1.) When discussing export issues, an ODT is required.
> 2.) Bug reports need to focus on one thing. A large, complex document that
> has several problems likely is a duplicate report in many ways.
>
> So a minimal ODT containing one item that doesn't round-trip properly is
> required. If that is done and no existing duplicate report is found, it is
> best to create it as a new bug report anyway instead of adding onto this
> one. So I'll close this one, since we already have tons of bug reports about
> textboxes and page styles.
>
> P.S. DOCX format doesn't have any concept of page styles, so the stylename
> is irrelevant and can't be round-tripped.</span >
Well DOCX certainly must have something because I've laid out books using MS
Word on Windows 10 because that is what someone "had" to have. Running left and
right page headers that were different based on chapter and left/right page
position.
If LO really is so crippled that __nothing__ can be trouble shot without first
creating an ODT, they the product needs to do the offensive thing Gimp has done
for the same reason. It most only save in ODT format. Everything else has to be
File->Export.
Right now LO has a File->Save-As that lets one choose the format. If it can't
do it right, then it shouldn't do it. Should only allow Save in ODT and only
export to other formats __after__ saving an ODT.
You see, this wasn't an export issue. This was File-Save-as issue. What you are
telling me is File-Save-as simply doesn't work. It stores something corrupted
without informing the user on the screen. Traditionally that is not how Save-as
works in any other package. It is how Export works in many different packages.
File->Save-as indicates to the user the format is accurately supported
internally and what they are actually seeing. File->Export gives no such
indication because it does not change the visible file name nor the file
actually being edited.
You can reduce your bug reports and obtain valid data by fixing the usage flow.</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>