https://bz.apache.org/ooo/show_bug.cgi?id=126990
--- Comment #3 from orcmid <[email protected]> --- (In reply to John from comment #2) > Created attachment 85563 [details] > An example .odt file which opens as "full of ######" > > This file is taken from > https://forum.openoffice.org/en/forum/viewtopic. > php?f=7&t=1532&start=420#p372812. > > Notes: > > 1 It is a .odt file, but it is not a zip file, and it has no internal > structure (no content.xml, manifest.rdf etc). > > 2 When the file is opened with a Hex editor, it is 27,605 Bytes, and each > byte is zero. > > 3 When the file is opened by Writer, Writer assumes it must be a flat, > ASCII TEXT file. Writer brings up the ASCII Filter Options pop-up. The > document then appears with 9,999 x "#" as word 1, a paragraph return; 9,999 > x "#" as word 2, a paragraph return, and the remaining "#" as word 3. > Presumably Writer has a 9,999 character limit on a word and adds the > paragraph return. [ ... ] I confirm the behavior with the example file. The particular file triggers the plaintext filter. If the file is opened, it will be presented as paragraphs having runs of "#" characters. (I assume, in this case, the hex 00 bytes are interpreted as unknown or inadmissable characters and "#" is used to indicate them.) I confirm that the file consists of 27,605 null (hex 00) bytes. What we need to know from Tina, who has had this experience more than once, is 1. When a previously-saved file was opened for further work, and it showed as all "####", did the plaintext filter show up first? Did she click OK and then see the all "#" document? 2. What can Tina report about the conditions under which the document was saved and later failed to open correctly? 3. Can Tina upload an attachment of the file that opened that way for her, exactly as it was when she tried to open it (not after accepting the plaintext filter). And, either way, Tina's document will not be recoverable. But the evidence she can provide may help us to eliminate or mitigate what the cause might be. -- You are receiving this mail because: You are the assignee for the issue.
