<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#c21">Comment # 21</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#c20">comment #20</a>) > (In reply to roland from <a href="show_bug.cgi?id=138694#c19">comment #19</a>) > 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. > > This multi-dimensional topic. If the original file being pure MSO, this > obvious valid case.. > It's not a multi-dimensional problem, it is architectural. If internally LO can only handle ODT, then it needs to save ODT and have all else be an export just like Gimp. The Gimp project went down this same path years ago. They couldn't get other formats quite right. (95% is still not quite right). The solution was an architectural change. It would only save and load whatever special format it used. Everything else was an export/import. By moving the other file types to an Export menu instead of Save-as, they removed the implicit believe that "things just worked." They also increased the likelihood the original file needed for debugging still existed. Product got better.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>