Evince doesn't rely on extension to determine file type. Briefly, what evince does (correct me if I'm wrong): 1. Try to determine file type based on uri with a call to "g_file_info_get_content_type" function. This function uses infos returned by GIO to determine mime type. 2. If it fails then try to determine mime type with a data sample, 3. Then call the backends manager with this mime type to process the file, 4. If the backends manager fails to open the document then print message "Unhandled MIME type : ..."
Hence, even if this process could probably be enhanced, I don't think this is a bug in the way evince determines file type. But sure, there is a usability issue and messages should be more user friendly. Evince should print a human readable description of the content type. For instance opening a non existent file returns the following message "Unable to open document. Unknown MIME type" instead of simply "File doesn't exist" I will mark this as "Invalid" tomorrow as I am confident this is not an issue in the way evince determines file type and open a new one for this usability issue. If you think this is unsatisfactory, please let me know and we can discuss what to do next. Regards, JB. -- .pdf fails to open: Unhandled MIME type: "application/x-ole-storage" https://bugs.launchpad.net/bugs/214076 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
