https://bz.apache.org/ooo/show_bug.cgi?id=118379
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #11 from [email protected] --- This bug still exists in 4.2.0. I attempted to replicate the bug on 9/22/2015. System environment: Apache OpenOffice Writer 4.2.0 - AOO420m1, Build: 9800, Rev.1692551 OS: Windows 7 Home Premium - SP 1 (64bit) CPU: AMD FX-8350 Eight-Core Processor GPU: NVIDIA GeForce GTX 970 Steps taken to replicate the issue: 1. Open file “Dienstreiseantrag_Cebit.doc” provided by original report. 2. Highlight “5. Voraussichtliche / geschätzte Reisekosten” with cursor. 3. Delete line, type “Lorem ipsum dolor sit amet” on the same field. 4. Click on the save button. 5. A prompt will appear asking whether to keep the file’s current format or save in ODF format. Leave “Ask when not saving in ODF format” checkbox checked and select “Keep Current Format”. 6. Close file. 7. Re-open file. 8. An error message will appear with the text: “Read-Error. This is not a WinWord97 file.” Clicking OK or the red X to close the dialogue will bring you to a blank “Untitled 1” unsaved OpenOffice Writer document. I observed the same file size loss as indicated by the original report. Original is roughly 117-120 KB. After saving, the file is only 52 KB in size. Microsoft Office 365 is actually able to read the corrupted file, but formatting is broken and certain characters don’t appear. I noticed that the file provided by the OP contained German text. I attempted to replicate this bug with my own created 100 KB .doc file but did not experience similar results. My own 32 KB .docx file also didn’t experience the same issue. I tried with both English and German text. As a last test, I selected all the text from the originally provided file and copied it into a new .doc file. Following the same steps listed above, the file was not corrupted. I speculate that actual text in these corrupted files is not the issue. Despite having to change a certain line or a certain string of characters for Writer to save the file, the actual issue likely lies within how Writer handles.doc/docx files. This could definitely be a severe issue for people using Writer on certain older documents. -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue.
