<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#c12">Comment # 12</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:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to roland from <a href="show_bug.cgi?id=138694#c11">comment #11</a>) > 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. The DOC/DOCX save quality is somewhere in the middle ground. Pretty OK for simple documents.. but changes with complex documents under circumstances.. Also there is the function mismatch. So LibreOffice ODT support things which DOCX can't do. So these get converted/transported in to something which matches DOCX specifications. Export instead as direct save would be by far more realistic, IMHO. It's not only about 'fully supporting' DOCX format (not the case). But also LibreOffice not having the same function set. So it will never 'fit'/match exactly the DOCX specifications. However there number of different views about that.. So say DOCX export being good enough.. and there is a warning dialog at save (which can be dismissed).. Also there is proposed a way make clear what the incompatibility's are. But pretty complex and likely even an pretty long list. In my world.. DOCX will be imported (silently converted to ODT) and saved as ODT. Only File -> Export to DOCX/ODT/RTF. (Like Apple Pages). And there is a group who like to 'read the manual' approach. You got a tool, which behaves a certain. You have to learn to use it. Even if the tool putting things straight into your face which you shouldn't do at all. Personally bit more of nudging/teaching application. So me +1 'Export' instead of direct save. But this might be less comfortable for some.. and people not familiar with the concept can't find DOCX anymore. Or people disliking not being able to directly save into DOCX (more cumbersome) Or Export being seen as lack of trustworthiness in DOCX/DOC. Kind of 'degradation'. Current approach is to keep people in the illusion the can safely save into DOCX/DOC (without any compromise). And kind of scoffing at those who do and start complaining about something being broken. People should make backups.. people shouldn't save directly into DOCX etc.. Solutions would be.. sidecar (with double save. ODT/DOCX). Or Export. But of course matter of file management comes into play. Multiple documents on you're system (DOCX/ODT).. Which one is the one (especially if DOCX is shared with Word users.. and send back etc). So at minimum a setting must be in place to restore the 'current' behavior. However this should be deliberate choice less advised (to be used at own risk)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>