Created attachment 126568 [details] DB Spec for Snee project I get this error message on opening the attached file: File format error found at SAXParseException: '[word/document.xml line 2]: Attribute w:eastAsiaTheme redefined', Stream 'word/document.xml', Line 2, Column 89396(row,col). Seems to be similar to https://bugs.documentfoundation.org/show_bug.cgi?id=92157, which is now closed. Tried downgrading to 4.4.7 as recommended here https://bugs.documentfoundation.org/show_bug.cgi?id=97063, but the file only partially loads - most of the text is lost. I also tried looking at the docx's document.xml file, but there is no "Attribute w:eastAsiaTheme" at Line 2, Column 89396. I also tried the solution here https://bugs.documentfoundation.org/show_bug.cgi?id=97063#c8 - but it didn't work. I get a 'General I/O error' message when trying to open the file. Please help - there are day's of work in that file! Thanks
Well I've recovered the file. I went through this process again, https://bugs.documentfoundation.org/show_bug.cgi?id=97063#c8, I guess more carefully this time, and I've got the file back. The bug's still there, though.
It opens ok in 3.6. Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.0.0.alpha0+ Build ID: f3d26af51588af441f62fb69bb7a5432845226ac CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on August 5th 2016 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
Bisecting will just show... https://cgit.freedesktop.org/libreoffice/core/commit/?id=ebf767eeb2a169ba533e1b2ffccf16f41d95df35 writerfilter: DOCX import: better error handling than "catch (...) {}" If there is a SAXParseException, OOXMLDocumentImpl::resolve() should not ignore it, which would just get you back to silent truncation The xml is indeed invalid so the problem took place at save, not load. The docProps/app.xml claims LibreOffice 5.1.4.2 so the generator seems to be us so apparently at least in that version we have a save bug. Taking the document and stripping out the invalid tags and resaving it as docs in 5.1 gives a well formed document so I can't tell what the circumstances are to reproduce the invalid generation. Is this a document exported from another source document ?
*** Bug 97063 has been marked as a duplicate of this bug. ***
I can't be 100% sure but I think the document was created in Word by another user, passed on to me, who worked on it in LO 5.1.4.2 for a few days before it got corrupted.
Adding Cc: to Michael Stahl
Created attachment 128311 [details] File corrected After having decompressed the file then used this tidy -utf8 -xml -w 255 -i -c -q -asxml on word/document.xml I recompressed the file and could open it on LO built from master sources updated today. Could you give it a try?
I guess this can be closed as RESOLVED DUPLICATE of 99227 as both were introduced by the same commit *** This bug has been marked as a duplicate of bug 99227 ***
Xisco, if you think of DOCX import: better error handling than "catch (...) {}", then it's not relevant for a duplicate. As explained before, it's just better handling of existing errors. I'd rather mark this one as Invalid because there is no source document, nor the steps to reproduce (like: save DOCX in LO).
*** This bug has been marked as a duplicate of bug 96878 ***
*** Bug 102131 has been marked as a duplicate of this bug. ***