empty files are reported as text/plain
I'd like to re-open this discussion:
Ignoring the file suffix for empty files is incorrect IMO. An empty .mp3 might be incorrect, but lots of other file formats consider an empty file perfectly valid. This is causing problems for our users as their work flow has been to create an empty file, open it with our client by clicking on it, and then getting any changes saved to that file.
At the very least this text/plain behaviour should only be used if the file fails any content test that mime-type has. But probably not even then. I'd rather see the file opened with the expected application and it complaining the file is broken, than having an entirely different application opening stuff.