<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <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#c16">Comment # 16</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 <a class="email" href="mailto:roland@logikalsolutions.com" title="roland@logikalsolutions.com">roland@logikalsolutions.com</a> <pre>(In reply to Telesto from <a href="show_bug.cgi?id=138694#c15">comment #15</a>) > @UX > Please see <a href="show_bug.cgi?id=138694#c13">comment 13</a> - the preview DOCX save/export might be something to > consider. Maybe even useful for automatic testing No, I'm not volunteering to code it, but speaking as someone who has done a lot of development over the past three decades, I would think the out-and-back for non-odt format would be the easiest thing. You would just be gluing together things already in place. Yes, you could have a difficult time telling whether out or in was what went off the rails, but at least one would have a heads up about the potential problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>