<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<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#c19">Comment # 19</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>Well, I hate to break it to you, but your aim isn't even close to hitting the
target. Don't even get me started on the picture support.
If the __only__ way your developers can debug anything is starting with an ODT
then the architecture of OO is completely wrong. It needs to follow the
architecture of Gimp. Only support a single native file format and make the
user export to others so the user knows it is a crap shoot.
Look back through this thread. I "trusted" what you said to be true. That's
what your current architecture implies. The output wasn't even within hand
grenade distance of being correct. When I provided the .docx I was asked for
the original ODT. There was no original ODT. The architecture of the
application did not force that and there was not massive warning dialog saying
I need to also save in ODT if I want to have any hope of someone fixing the
inevitable issues.
I ended up having to boot a laptop with Windows 10 on it and use MS Word to
create a new resume because OO simply couldn't do it.</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>