[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #1 from Steven Lott --- Created attachment 84760 --> https://bz.apache.org/ooo/attachment.cgi?id=84760&action=edit Another Sample Corrupted FIle This is another corrupted file. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 Steven Lott changed: What|Removed |Added Attachment #84760|0 |1 is obsolete|| --- Comment #2 from Steven Lott --- Created attachment 84761 --> https://bz.apache.org/ooo/attachment.cgi?id=84761&action=edit Another Corrupted File A second example of a corrupted file. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 oooforum changed: What|Removed |Added CC||ooofo...@free.fr --- Comment #3 from oooforum --- Provide a corrupted ODT document doesn't help. Thanks to attach the original docx file. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #4 from Steven Lott --- Created attachment 84767 --> https://bz.apache.org/ooo/attachment.cgi?id=84767&action=edit Sample file before editing and saving. Sample file before corruption. Note that it was heavily edited, so there's almost no relationship between this file and the corrupted file. But it was requested. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #5 from oooforum --- Created attachment 84768 --> https://bz.apache.org/ooo/attachment.cgi?id=84768&action=edit Your docx has been converted without problem as ODT I don't reproduce. a) Open the .docx b) Save as .odt c) Close document d) Open the .odt Result: no corruption -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #6 from Steven Lott --- That's not what I did. I'm not surprised that a simple, no-edit conversion happened to work. Please actually look at the corrupt files. They don't load. My sequence was this. 1) open the .docx 2) edit heavily. 3) save as .odt. This leads to corruption. Please look at the corrupt files to see that they are corrupted. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #7 from oooforum --- Please provide more details about step 2. What kind of "heavy" handling did you set? -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #8 from Steven Lott --- Sorry. Didn't take notes. Change tracking was on, so the details are readily available. If only the file wasn't corrupt. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #9 from oooforum --- (In reply to Steven Lott from comment #6) > My sequence was this. > 1) open the .docx > 2) edit heavily. > 3) save as .odt. Not good Try as my comment 5 -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #10 from Steven Lott --- Good advice. However. It doesn't uncorrupt the file. Nor does it fix the bug that corrupted the file. It may be a good way of avoiding the corruption bug, but it doesn't fix the bug that corrupted the file. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 oooforum changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #11 from oooforum --- DOCX format is proprietary and undocumented and some advanced features may not be available in Writer. Also, some Users have experienced crashes with large (100's of pages) or complex documents. So the best way to avoid problem is to convert in ODF in first time. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #12 from Steven Lott --- This advice doesn't fix the problem with these documents and doesn't correct the bug that lead to the corrupted documents. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 Steven Lott changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED --- Comment #13 from Steven Lott --- This is neither resolved nor fixed. The files are corrupt. The procedure given does not fix the corruption. The files remain unreadable. No bug has been identified in the software, so this problem will continue to occur. It is not resolved. It is not fixed. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 Regina Henschel changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||rb.hensc...@t-online.de Ever confirmed|0 |1 --- Comment #14 from Regina Henschel --- There are different problems. File B03671_06_1d_SFL copy.odt (Sample Corruptes file) has a real problem. It is a duplicate attribute at position 5262 in line 2 in the part content.xml. You can enter the package (e.g. with 7zip) and remove the duplicate attribute. Then the file will be readable. Such error happens from time to time, but there is no reproducible scenario up to now, and therefore it is not possible to nail it down to a place which needs to be fixed. Searching in internet will give you some instructions, how to repair such files. For the attached one I can send you a repaired version, simple drop me a note. The file B03671_02_2d_SFL copy.odt (Another Corrupted File) has a different problem and I will take this report for it. You can open the file with an older versions like AOO 4.0 or OOo3.2. and resave it with that version. Then the resaved version is readable in the current AOO too. You can install the older AOO version "administrative" (if necessary ask on forum) so that you can use it parallel to the current version. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 Armin Le Grand changed: What|Removed |Added CC||armin.le.gr...@me.com --- Comment #15 from Armin Le Grand --- Could you mention which attribute is duplicate? Is it the same or does it change from case to case? This might give hints in following the creation of exactly that attribute -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #16 from Regina Henschel --- It is attribute office:name in node -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 Joe Smith changed: What|Removed |Added CC||j...@martnet.com --- Comment #17 from Joe Smith --- This looks like the same xml error that appears in Issue 126219 -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 orcmid changed: What|Removed |Added CC||orc...@apache.org --- Comment #18 from orcmid --- (In reply to Steven Lott from comment #0) > Created attachment 84759 [details] > Sample Corrupted file. > > Corrupted file. This started as a .docx file, which was then saved as an > .odt file. (In reply to Steven Lott from comment #2) > Created attachment 84761 [details] > Another Corrupted File > > A second example of a corrupted file. I confirm that Attachment 84767 (B03671_02_2d_SFL copy.odt) fails to open with Apache OpenOffice 4.1.2 running on Windows 10. However, the file does open in Microsoft Word 2016 without complaint. That is how I can determine that it is Chapter 2 of what appears to be the text of a programming book. This appears to be a peculiar case of AOO writing a document that it cannot itself read. I cannot determine how much of the document is presented by Word 2016. The .odt file has a complex structure involving embedded subdocuments. It deserves further exploration. The workaround for these situations is to save the .docx as an .odt *before* any editing, while one has the opportunity to see whether there is any loss of fidelity before going farther. That does not alter the fact that there is a confirmed problem here. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 orcmid changed: What|Removed |Added Latest|--- |4.1.2 Confirmation in|| --- Comment #19 from orcmid --- (In reply to Steven Lott from comment #0) > Created attachment 84759 [details] > Sample Corrupted file. > > Corrupted file. This started as a .docx file, which was then saved as an > .odt file. This is rather different than the second attachment (B03671_02_2d ...). Fie B03671_06_1d_SFL copy.odt fails to open in both Microsoft Word 2016 and Apache OpenOffice 4.1.2 on Microsoft Windows 10. In both cases there is claimed to be a defect in one of the data streams in the .odt package. The AOO error message is the most informative and not that great: Read-error. Format error discovered in the file in sub-document content.xml at 2,5261 (row,col). There are 11 sub-documents and I notice that the top-level content.xml (the only one big enough) has extensive tracked changes, many involving annotations. The Zip package checks as complete and without Zip-level defects, so this appears to be a more serious case in that the document was completely saved, but with a defect in its formatting. Although of no consolation, this is enough to exclude these two cases from Issue 126869. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #20 from orcmid --- (In reply to orcmid from comment #19) > (In reply to Steven Lott from comment #0) > > Created attachment 84759 [details] > > Sample Corrupted file. > > > > Corrupted file. This started as a .docx file, which was then saved as an > > .odt file. > > This is rather different than the second attachment (B03671_02_2d ...). I failed to notice that Regina had already analyzed this one in Comment 16 and the error is an element with a duplicate attribute, making the XML invalid. This is a very different bug that deserves its own issue. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #21 from orcmid --- (In reply to orcmid from comment #20) > (In reply to orcmid from comment #19) > > (In reply to Steven Lott from comment #0) > > > Created attachment 84759 [details] > > > Sample Corrupted file. > > > > > > Corrupted file. This started as a .docx file, which was then saved as an > > > .odt file. > > > > This is rather different than the second attachment (B03671_02_2d ...). > > I failed to notice that Regina had already analyzed this one in Comment 16 > and the error is an element with a duplicate attribute, making the XML > invalid. > > This is a very different bug that deserves its own issue. In the case of the second attachment only, this is the same issue that Regina has described in detail in Issue 126339. I am not certain that should be treated as irreproducible, since it is a confirmed and identified error in the file that is produced. There is no requirement that we be able to cause it with external testing. We know there's an error. -- You are receiving this mail because: You are the assignee for the issue.
[Issue 126339] Corrupted Files
https://bz.apache.org/ooo/show_bug.cgi?id=126339 --- Comment #22 from orcmid --- (In reply to orcmid from comment #21) > (In reply to orcmid from comment #20) > > (In reply to orcmid from comment #19) > > > (In reply to Steven Lott from comment #0) > > > > Created attachment 84759 [details] > > > > Sample Corrupted file. > > > > > > > > Corrupted file. This started as a .docx file, which was then saved as an > > > > .odt file. > > > > > > This is rather different than the second attachment (B03671_02_2d ...). > > > > I failed to notice that Regina had already analyzed this one in Comment 16 > > and the error is an element with a duplicate attribute, making the XML > > invalid. > > > > This is a very different bug that deserves its own issue. > > In the case of the second attachment only, this is the same issue that > Regina has described in detail in Issue 126339. I am not certain that > should be treated as irreproducible, since it is a confirmed and identified > error in the file that is produced. There is no requirement that we be able > to cause it with external testing. We know there's an error. I am getting the cross-reference backwards. Another issue on this duplicate attribute error is Issue 126479. -- You are receiving this mail because: You are the assignee for the issue.
