After saving an .odt file in writer with lots of comments, the file cannot be opened anymore (Lesefehler: Formatfehler).
After unzipping the file and editing content.xml, I discover that there is a "style" tag which has two "office:name" attributes with identical values.
This has happened twice with the same document. (I can provide the document but it is kind of semi-confidential, don't want to upload it here).
Please let me know if you need any further information!
Sorry, forgot to include version:
on Ubuntu 14.10 64 bit, German language
(In reply to Titus Stahl from comment #0)
> This has happened twice with the same document. (I can provide the document
> but it is kind of semi-confidential, don't want to upload it here).
You could try this: https://wiki.documentfoundation.org/Anonymizing_a_document#Sanitize_file_text
Set to NEEDINFO.
Change back to UNCONFIRMED after you have an example file for us. Thanks.
Created attachment 117709 [details]
this is a testcase. basically, if I change anything in the document and save it, it cannot be opened anymore.
on Ubuntu 15.04, 64-bit
Created attachment 117902 [details]
Small document with changes and notes: example of an opening error.
This type of error is very common if you keep changes and notes in the same document. Changing notes will very, very often crash the document.
Went back from 5.0 to 4.4 because of the large number of crashes with documents like these.
Running on Ubuntu 15.04 64 bits.
a regression from the AOO imported range annotation feature,
this was fixed in LO 4.4.4 by
Author: Caolán McNamara <email@example.com>
AuthorDate: Wed Apr 22 14:10:38 2015 +0100
fix assert on export of ooo63141-1.doc to odt
if bAutoStyles is true then the mbDoSomething of the SvXMLElementExport is
false, and the ctor/dtor doesn't do anything so any attributes added to the
exporter are not cleared by the SvXMLElementExport dtor
so only add the attribute if bAutoStyles if false and might as well extend the
block to cover the use of SvXMLElementExport and use the other ctor which
defaults mbDoSomething on
*** Bug 90330 has been marked as a duplicate of this bug. ***