Created attachment 57053 [details]
The clean document
LibreOffice 3.5 corrupts my DOCX files completely, so that Microsoft Word 2010 cannot open it anymore!
I tried it with simple documents and it failed completely. Word doesn't even offer to recover the document, it is just unable to open it. I think this is a huge issue for most users of LibreOffice.
On Ubuntu 64 bit, with LibreOffice 3.4, the documents were only corrupted, so that Word had to recover it (with lots of lost formatting...) but it could open the file.
I experienced a similar behaviour with xlsx, too.
I don't know, why the importer for docx/xlsx is getting worse. I hope, you guys can use this information to improve LO.
I attached one clean document and the result as I saved it with LO 3.5 on Windows. The corrupt one is not recoverable under MS Office 2010.
Created attachment 57054 [details]
The corrupt document
The document you attached is a (perfectly good) ODT file with a wrong .DOCX extension.
Can you describe the exact steps that caused to create this file?
I created the clean document on Windows 64 Bit with Microsoft Office 2010. I saved it and then opened it in LibreOffice 3.5 (also on Windows 64 Bit, but it's the LO 32 bit version).
Then I removed a blank and added it and saved the changed document under a new file name, but with .docx suffix.
Then I tried to open this new docx file with Word and it says it tries to recover it, but it fails. The document is not readable with Word.
I hope this is enough information. If you need more information, just ask.
Though I have no windows for testing, I'm seemingly able to produce a file in docx format (i.e. exactly like the clean document) when saving the clean document as described in the report:
1. open clean.docx
2. modify it (add a word)
3. save by pressing save button
4. confirm fileformat dialog
So all works as expected on linux rpm-32 LibO 3.5.0rc3.
Seems as if "saving" the document did not produce a document of type "MS XML" but rather of type "ODT". Adding the file extension ".docx" does not automatically change the document type. To be able to tell, if this was caused by a software misbehavior (bug) or by a somewhat "not-as-designed" user action, the question is, how the "corrupted document" was created exactly and if this behavior can be reproduced (and under which conditions, i.e. OS/platform/etc). So you should give exact step-by-step instructions, what you did (which button you pressed, and so on) to save the document. Then somebody (using the same Platform if available) should try to reproduce the behavior.
(In reply to comment #4)
> @ Philip:
> Seems as if "saving" the document did not produce a document of type "MS XML" but rather of type "ODT". Adding the file extension ".docx" does not
> automatically change the document type. To be able to tell, if this was caused by a software misbehavior (bug) or by a somewhat "not-as-designed" user action,
> the question is, how the "corrupted document" was created exactly and if this behavior can be reproduced (and under which conditions, i.e. OS/platform/etc). So
> you should give exact step-by-step instructions, what you did (which button you pressed, and so on) to save the document. Then somebody (using the same
> Platform if available) should try to reproduce the behavior.
Thank you for the test and the clarification! I will try it if I did use the wrong format and report back (propably this evening).
Created attachment 57110 [details]
Clean document with TOC
Created attachment 57111 [details]
Corrupt document with TOC
I reanalyzed my problem and found the real problem corrupting the files.
The document is unrecoverably corrupted by LO 3.5, so that MS Word 2010 is not able to open the documents.
The source is the TOC, added by Word. I added two new documents (1 clean, 1 corrupt).
Here's the procedure, how I created them:
1. Create new document in MS Word 2010
2. Insert TOC (standard template)
3. Add some headlines
4. Refresh TOC
5. Save document as docx file.
6. Copy document with Windows Explorer.
7. Open copy with LibreOffice Writer 3.5.
8. Add a line break
9. Save it in the current format.
10. Open it in Word. Not recoverable (problem in Line 2, document.xml).
I compared the contents with WinMerge and the docx addon. I found the differences in the TOC area.
I really hope, this information may help you. I will edit the bug title according to the new information.
reproduced in 3.6.0 master 97fdf02-9eed775-f061262 on Fedora 64 bit
problem with import/export of table of content as described here:
Bug 46025 - Writer FILESAVE, FILEOPEN: docx files with "Content" field processed worng
@ Philip Gillißen
Thanks for bugreport.
I can confirm this bug also appears on Windows XP 64bit, with latest version of LibreOffice 126.96.36.199.
The file does not open in Word, and when opening in Libreoffice half of the original document is lost!
This is very serious bug, that leads to data loss! I changed the importance level accordingly.
I confirm this bug.
I'm having a very similar problem but without any TOC
Here is a clean .docx file and the corrupt version that has only been opened and "saved as" in LibreOffice.
This bug does not happen with every document (I have other examples of work/don't work .docx files) and save as in .doc has "resolved' the problem both times it appeared.
Mac OS X 10.8.1
Created attachment 66448 [details]
Original clean document
Created attachment 66449 [details]
Same results with LO 3.6.1 en-US (previous was fr)
Is there an update on this issue?
I think it's quite critical.
This also happens for LibreOffice 188.8.131.52 (build ID 350m1(Build:2) ) when I just add a table. If there's only a regular line of text, the saving to .docx works ok, but as soon as I add a 2-row, 2-column table (empty), the file becomes unreadable in Office 2007.
This is still happening in Version 184.108.40.206 with Windows 8.
Created attachment 77391 [details]
New test with Yves' document and master sources updated today
On pc Debian x86-64 with master sources updated today, I retrieved the clean Yves' file and did a "save as" with a new name. I attached the file.
I don't have MsOffice 2010 to test it but will attach console logs which show some problems.
Created attachment 77392 [details]
console logs with master sources
Following my previous comment, I attached console logs showing the messages during original file opening and during save as.
could someone tell if https://bugs.freedesktop.org/attachment.cgi?id=77391 can be opened with MsOffice 2010?
Opening 7503_testwithmaster.docx by msWord 2007 and 2010:
error opening /word/document.xml line 2 column 104255
(In reply to comment #21)
> could someone tell if https://bugs.freedesktop.org/attachment.cgi?id=77391
> can be opened with MsOffice 2010?
Yes, still causing the error for Office 2010 on Windows 7 (32bit). Get the same error message as Sarah.
Sorry! I meant Sasha.
I had this error from MS Word2010/Windows 7 Home Premium - 64 bit.
The file 7503_testwithmaster.docx cannot be opened because there are problems with the contents.
A document must contain exactly one root element.
Location Part: /word/document.xml, line: 2, Column: 104255
The file was not displayed.
LO 4.0.1 also failed to open it.
and LO 4.0.2 on Fedora 64 bit crashes during opening this file
When nothing else helps: Try to download SoftMaker FreeOffice (57MB, free office suite), it has fantastic import and export filters for all Microsoft Office formats. Never had conversion problems with FreeOffice, but regularly with LibreOffice. freeoffice.com
Let me add Miklos to see what happens ;-) it sounds bad.
When saving attachement 66448 to DOCX, I document.xml indeed isn't well-formed on -4-1. It's fine on master, I'll check what should we backport here.
http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-4-1&id=59d8dde3fc9a4dc653e43efb8552efc4ab3efc92 should take care of the well-formed output problem on -4-1
(In reply to comment #30)
> 1&id=59d8dde3fc9a4dc653e43efb8552efc4ab3efc92 should take care of the
> well-formed output problem on -4-1
Thank you for the fix!
I tested your patch with the current daily build (http://dev-builds.libreoffice.org/daily/libreoffice-4-1/Win-x86@6-debug/2013-08-27_09.28.10/) and the edited document is not corrupt and can be opened by Word without any complaint.
Thank you very much for your work, this is great!