https://bz.apache.org/ooo/show_bug.cgi?id=126869
--- Comment #30 from orcmid <[email protected]> --- (In reply to John from comment #29) > (In reply to orcmid from comment #28) > > Issue 126990 brings up the special case of a saved document that is found to > > contain only paragraphs of "#" characters. > > > > It can be addressed separately there. This is entirely different than cases > > where the file is damaged or otherwise unreadable. The file of all "#" > > content in one or more paragraphs is completely valid and readable. It just > > isn't what the user saw as the document being saved. > > A slight correction ... > > A .odt file of all "#"' does not have any structure and cannot be unzipped. > > When the .odt is opened with a Hex editor, each and every character in the > file is 00. I will upload such a .odt file of all "#"' at Issue 126990. > [ ... ] I have personally verified files that open without difficulty and yet present paragraphs of all "#". I inspected the .odt, which was a valid Zip, and valid ODF, and the content of each paragraph element was a lengthy run of "#" characters. I have not, on Windows, ever seen a corrupted .odt that does not look like a Zip in any way shape or form open at all. There might be something that triggers the ASCII filter (what kind of text file is this?) sort of thing, but I have not personally witnessed that with a file of all 00 bytes. I am very interested in seeing such an attachment at Issue 126990. Thank you. I am not disputing the reported observation. I am suggesting that there may be two different situations that have similar symptoms but are quite different. It could even be the case that the file I inspected at the binary level was a fabrication or an incorrect save of a file that opened badly, so it was not the actual defective file. Only by gaining more information from users, preferably with the defective file attached, can we provide certainty. -- You are receiving this mail because: You are the assignee for the issue.
