To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=82902
------- Additional comments from [EMAIL PROTECTED] Thu Nov 1 23:37:49 +0000 2007 ------- > The bug is a "time bomb". It depends on how often you have saved > your document. I might add that there must be other factors besides simply the number of writings of the document to disk. Let's say, version n-1 (with n = number of writings to disk) could be opened, and version n became corrupted; then I fell back to version n-1 and reconstructed my changes from version n manually, then I continue to work with version n-1+x (x = additional changes), which becomes (currently) version n+11 and still loads fine. Since I re-did all my edits, and the number of disk-writes of version n+11 clearly exceeds n-1, there IMHO is most probably is something else involved (autosaves shouldn't fall into account since I don't leave the document open when I'm not working on it, and it's set to the default setting of 15 minutes; I definitely do save manullay more often, which resets the autosave counter, right?). Also, I changed the setting for "Optionen/Laden-Speichern", "XML-Format auf Größe optimieren" to "unchecked" with the last reconstructed version of the document from one week ago; the last 46 versions (= not version control, but manually created "derivates" of the file with one new file per day, yyyy-mm- dd.odt plus additional "subversions", counting from yyyy-mm-dd_a.odt to yyyy-mm- dd_z.odt) of the file were written with this setting, which _did_ _not_ prevent the new corruption; however, content.xml is now indeed better readable and editable when opening with an text editor. Regarding the hint from the mailing list (OOo encoding "_"-characters cumulatively when writing the file), I don't quite understand how I could influence what OOo is enconding or writing; also, Validome did and does not point to constructs like the mentioned "_5f_5f", and reducing this string wouldn't let me open the second corrupted file (I didn't try it on the first corrupted file). However, in the current (the two times manually reconstructed) document, I did a replacement of "_5f_5f" with "_5f" in content.xml (sums up to a total of 16.376 replacements) and wrote this back to the odt/zip file, which at least did not seem to harm the file. Would it be advisable to do this from time to time? Thanks & regards, -asb --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
