https://bugs.documentfoundation.org/show_bug.cgi?id=133627
--- Comment #20 from PMouse <[email protected]> --- Very interesting. Working Example saved in MSO 2016 produced the same first error: "Word found unreadable content in '<document>'. Do you want to recover the contents of this document?..." However, if I click "yes", the document is shown, a little messed up, but functional. Whereas, the same document exported by LO 7.2.5.2 cannot be converted, apparently, and MSO2019 suggests using the software marketplace to find software to help, but never successfully opens the document. I also tried converting the MWE I provided to ODT with LO, closing it, reopening it, and saving it as .docx. That docx version produced the same two errors as the MWE, which was never saved as ODT. But, the .odt document, in between, produced the same result in MSO2019 as the MSO2016 document you posted. Meaning, MSO2019 generates the error: "unreadable content" when opening the .odt version, but *is* successfully able to "recover" a usable document. I'm loosing track of where all this evidence leads. There is clearly a disagreement between LO v6.4-v7.2 and MSO2019 about the correct .docx format re: images or maybe floats, still not sure what is the core issue. In LO7.2, this disagreement doesn't result in a crash of MSO2019, which is an improvement, but it is still not interoperable. -- You are receiving this mail because: You are the assignee for the bug.
