Apache OpenOffice (AOO) Bugzilla – Issue 69970
WW6: export corrupts diacritical symbols
Last modified: 2017-05-20 11:15:32 UTC
This issue makes transition from M$Office97 (and older) hard enough, because there are many documents saved in WW6 format (at least in our office). Works like this: The file is opened fine. However saving it corrupts many diacritical symbols. Issue is very malicious, because user dosen't know about the problem. He can do much editing on the file, then he saves it and closes OpenOffice.org in good faith everything is OK. This time, the data are already corrupted and for the user, impossible to repair. User notices this only the next time, trying to open the file. Hours of work lost, often the file is in worse condition than it was before the editing. This issue could be also MIS-interpreted as IMPORT problem, however data are corrupted upon SAVING (export filter) in fact.
Created attachment 39448 [details] Original file saved from M$Office97 as Word6.0/95
Created attachment 39449 [details] The file opened and then saved from OOo2.0.3 -diacritics is corrupted. File size grows 8x.
Created attachment 39450 [details] Screenshot of both files in sk_SK localized environment
Created attachment 39451 [details] Additional document to show problem
MRU->HBRINKM: Also see my additionally attached document. when exporting this to WW6 format and reopening, many characters turned into Questionmarks.
I'm glad to see the issue accepted and designed, however isn't this exactly the case of (cite): "User data is corrupted in an easy-to-encounter way; e.g. saving a document corrupts the resulting file and renders it unusable" ?
I'm asking just to clarify things. IMO, a file corrupted such a way is REALLY no longer useful. Searching the corrupted symbols and replacing them is usually possible only manually, and this is so time consuming, that writing the document from the scratch could sometimes be more viable solution. What is even worse, experience shows, that users usually DO the manual repare, save the document again, and inevitably see it corrupted again when they open it next time. This is quite cruel.
according to release status meeting: target 3.x
.
@mba: is there an analysis of this error available and also an effort estimation ?
*** Issue 107946 has been marked as a duplicate of this issue. ***
*** Issue 115585 has been marked as a duplicate of this issue. ***
Reset assigne to the default "issues@openoffice.apache.org".