Issue 123868 - Detect a null file instead of asking for import filter
Summary: Detect a null file instead of asking for import filter
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 4.0.1
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-17 16:50 UTC by bmarcelly
Modified: 2013-12-18 05:39 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Typical null file created by OpenOffice (31.80 KB, application/vnd.oasis.opendocument.text)
2013-12-17 16:50 UTC, bmarcelly
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
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
.