Correct opening of documents

[teamamaze]

Correct opening of documents

[lbdroid]

It is possible that this could be due to a flaw in the mechanism used to distinguish between binary and ascii text files. Like many binary files, there are ascii elements, in particular, the header used to define the file type.

[lbdroid]

Uh huh... Futils.java lines 528 or 532.

Actually, it would be nice to be able to disable all the built-in file handlers altogether, since there are a lot of applications capable of opening all of the types that the built-in handlers are able to open. While it is nice to have a fallback, these handlers are somewhat simplistic. Sometimes it is nice to hand the file over to applications that are devoted to that specific function.

For example, you don't want gedit or windows notepad to take over all text file handling on a desktop, rather something more powerful, like vi, emacs, notepad++, etc. Same on Android.

I would really like the option to NOT USE the integrated file handlers. Instead of loading activities to handle these files internally, handle everything as "openunknown". Create intent filters for the internal handlers, and let the system choose whether to let the file manager handle them, or some other application.

[lbdroid]

Icons.java defines a whole bunch of non-plaintext files as "text", presumably for the purpose of selecting an icon to display. Futils.java queries Icons.java and is mislead into believing that those types should be loaded as plaintext. Icons.java:179-189 are the offending lines causing this problem. Registering intent filters with the system would avoid this entire problem by passing mimetype and uri to the system to deal with, instead of making bad assumptions.

[lbdroid]

Temporary hack fix; move what is currently on line 178 of Icons.java down to line 189. This would redefine all those word processor document as.... word processor documents.