Issue 123868

Summary: Detect a null file instead of asking for import filter
Product: General Reporter: bmarcelly <marcelly.bernard>
Component: uiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Normal    
Priority: P3 CC: elish, issues, oliver.brinzing
Version: 4.0.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
Typical null file created by OpenOffice none

Description bmarcelly 2013-12-17 16:50:45 UTC
Created attachment 82123 [details]
Typical null file created by OpenOffice

Sometimes (e.g. accidental PC power off) OpenOffice destroys a document and changes it to a file containing only bytes of value zero, see Bug 107487. Next attachment is a real corrupted document (I just changed the file name).

Problem : When opening this junk, OpenOffice asks the user a filter to read it ! The average user then supposes that the document still contains something, selects an ASCII filter, and OpenOffice displays pages of hashes.

Request for improvement : when a document is obviously destroyed, at least a warning message should be given. In the case of a document starting with lots of zero bytes, OpenOffice should say that the document contains nothing readable.
Comment 1 Edwin Sharp 2013-12-17 18:26:40 UTC
A warning message is a good idea, but not sure about a document starting with lots of zeroes.
Comment 2 Oliver Brinzing 2013-12-18 05:39:15 UTC
.