<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Export: Input list with empty item makes DOCX that can't be opened in Word - Generates XML parsing error" href="https://bugs.documentfoundation.org/show_bug.cgi?id=140018#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Export: Input list with empty item makes DOCX that can't be opened in Word - Generates XML parsing error" href="https://bugs.documentfoundation.org/show_bug.cgi?id=140018">bug 140018</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to Dave Potter from <a href="show_bug.cgi?id=140018#c5">comment #5</a>) Unfortunately, this is not that simple. The problem arose in a real life. I can't find out the steps to repro the problematic document from scratch, but it doesn't mean that it should be closed. There might be some sequence in LO, or there might be some way to create that in other applications (that we don't control). The bugdoc file is a valid ODF, and thus if some (external?) entity is able to produce it, it is expected that LO does not misbehave when processing such files. If it has such input, and exports it to DOCX, it must produce a valid output.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>