
Writer brings up the ASCII Filter Options pop-up.
RECOVER OPENOFFICE DOCUMENT ZIP
odt file, but it is not a zip file, and it has no internal structure (no content.xml, manifest.rdf etc).Ģ When the file is opened with a Hex editor, it is 27,605 Bytes, and each byte is zero.ģ When the file is opened by Writer, Writer assumes it must be a flat, ASCII TEXT file. odt file which opens as "full of #"ġ It is a. This issue is for tracking the "#" issue only.Īn example. The forum topic includes some cases beside the "#" case.

"Hagar Delest has carefully listed the posts where users have lost data at 22 pages term paper replaced with pound signs, where he has collected over two hundred (224 to date) cases." That is at I failed to find an existing separate issue about it. I am extracting the essential information here so we have an identified issue for this individual case. This is the first of the cases identified in Issue 126846. If you want, you can upload the file as an attachment here, and we can inspect it to confirm whether there is recoverable content. This precaution works for a number of other problems as well. Then you at least can fall back to the one you made the failed one from. The best precaution is to not save over the previous copy but save with a new name (put a date in the name or use a sequence number). When this happens, however it happens, that is really the content of the file and that is all there is. > I saved a file not 2 hours ago and when I opened it again the format was


(In reply to tinaconroy0718 from comment #0)
