attachment 117231 [details] is actually only comments.docx.
Before attaching the .zip, could you try with an up-to-date version (4.4 or 5.0 RC4)?

If using an older Ubuntu, you can get the latest stable from a PPA maintained by the Ubuntu team:

sudo add-apt-repository -y ppa:libreoffice/ppa

sudo apt-get update

sudo apt-get dist-upgrade 

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.

Created attachment 117685 [details]
File containing test comments with different formatting types, appears to be handled well.

Sorry about the zip, my bad. The docx was the important one anyway. 

I've updated to 5.0.0.5, and it does seem to fix the comment creation problem.

However, the file generated using 4.2.8.2 that led me to make this report can't be opened with libreoffice 5.0.0.5. 

4.2.8.2 would open the file, but corrupt all of the comments following the problematic one. Now, upon opening, I instead get an error message:


LibreOffice 5.0.0.5
 
File format error found at 
SAXParseException: '[word/comments.xml line 2]: Attribute w:hAnsi redefined
', Stream 'word/comments.xml', Line 2, Column 1215
SAXParseException: '[word/document.xml line 2]: unknown error', Stream 'word/document.xml', Line 2, Column 20452(row,col).


I can provide the file (and/or extract the xml comments) but they contain sensitive information so I would need to know they'd be held in confidence.

Similar story for me. Nightmarish experience trying to move images & comments, definitely pasted text from comment to body & the opposite. Also pasted text from image caption to another image caption. Ended up having to strip out all XML with the command line and get my work out in textfile.

Hello,

this is also observed here in Libreoffice 5.0.4.2, in Windows.

After some cut and paste, the w:cstheme tag is duplicated in the rFont tag. I can find the duplicate in this case in VI using the search pattern:

rFonts[a-zA-Z:" =]*cstheme[a-zA-Z:" =]*cstheme

I imagine something similar can be used to identify breaks caused by other duplicate tags.

Nevertheless, this doesn't explain why the problem happened and how it can be fixed.

Cheers,
Danilo

Ok, setting to NEW.

I have the same problem with version 4.2.8.2.
Copying text that has a link to a comment into a comment creates an ill formatted comment, at least in docx documents.

I can manually correct the file corruption (see below), but of course it would be better if it did not occur.

To reproduce the problem:
1. Create a new (empty) document.
2. Write some text in it.
3. In a part of the text add a comment (I selected some of the text and used the shortcut ctrl+alt+c).
4. Type some text in the comment.
5. Type more text in the (main) document (otherwise when you save the comment may not be updated, but that's a different bug).
6. Save the document in a docx format.
7. Close LibreOffice and open the document again (everything should be as it was).
8. Copy some of the text including all the text that is linked to the comment (I used ctrl+c).
9. Paste it in the comment (I used ctrl+v).
10. Write some more text in the main document (again to be sure that the comment will be updated when you save it).
11. Save and close the document.
12. Open it again.
The comment should loose some information that was there before, namely the author and date. If you open the comments.xml file inside the docx document you'll see that there are repeated tags inside the last comment which LibreOffice can't process correctly.

To solve it:
In Linux, the way I've been able to workaround and correct corrupted docx files. I make a copy of the docx file (make a backup!) and open the file with Archive Manager, extract comments.xml, open it with a text editor, delete the duplicate tags and replace the corrected version of comments.xml inside the original docx file.


By the way, the comments.xml is horribly formatted: everything in one line. I suggest that LibreOffice adds some newlines after each tag. Bonus points if indentation of the xml is properly done.

(In reply to Ertxiem from comment #7)
> 
> To solve it:
> In Linux, the way I've been able to workaround and correct corrupted docx
> files. I make a copy of the docx file (make a backup!) and open the file
> with Archive Manager, extract comments.xml, open it with a text editor,
> delete the duplicate tags and replace the corrected version of comments.xml
> inside the original docx file.
> 
> 
> By the way, the comments.xml is horribly formatted: everything in one line.
> I suggest that LibreOffice adds some newlines after each tag. Bonus points
> if indentation of the xml is properly done.

This method also allowed me to fix the corrupted file. I also second all of these points about the xml formatting, it's a mess to wade through and find the errors.

With last stable LO version 5.2.2, could someone give step by step process to produce a corrupted file from a clean file?

Indeed, taking a look to comments, quoted versions are EOL and it seems corrupted files have been fixed.

Let's assume it's a duplicate of bug 113790.

*** This bug has been marked as a duplicate of bug 113790 ***