<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - --convert-to fails with corrupted files" href="https://bugs.documentfoundation.org/show_bug.cgi?id=133472#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - --convert-to fails with corrupted files" href="https://bugs.documentfoundation.org/show_bug.cgi?id=133472">bug 133472</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>It's interesting why did it pass previously (when correctly warning in UI). Now it behaves consistently with other corrupt documents. E.g., see <a class="bz_bug_link bz_status_VERIFIED bz_closed" title="VERIFIED FIXED - SAXException: [word/document.xml line 20] when you try to open a document from Word 2007-365 (*.docx) format created with LO with a image copy from Draw" href="show_bug.cgi?id=128820">bug 128820</a>, where the DOCX from <a href="http://bugs.documentfoundation.org/attachment.cgi?id=155841" name="attach_155841" title="All documents and image with exception message">attachment 155841</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=155841&action=edit" title="All documents and image with exception message">[details]</a> was already not converted before the said patch. --convert-to must not silently process corrupted documents - at least I think so. My point of view on if we should allow that in --convert-to might be wrong; and if so, a separate bug needed to allow processing invalid files (as if user accepted), or add some additional switch to do that... (personally I still consider that wrong, because that would make processing unstable).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>