The bug has been opened on https://launchpad.net/bugs/91488 "Binary package hint: shared-mime-info I have some KDC files here (Kodak RAW files) and the new shared-mime-info recognizes them as such, but the default app that opens with them is f-spot. There are some other apps that are registered to open TIFF files (RAW files are kinds of tiffs, but not exactly), but these apps should not be there in the nautilus submenu at all, because they can not handle any kind of RAW file. ..." Not listing it as a subclass of "image/tiff" doesn't work neither because the mimemagic detects a tiff file which doesn't match the .kdc and nautilus refuses to open it then
The TIFF subclassing was introduced by a patch in bug 8170. CCing Udi Fuchs and Stanislav Brabec.
There is no easy solution. If the subclassing will not be here, Nautilus will reject to open KDC files and report MIME type conflict. If it is there, Nautilus offers image viewers in the second order in the menu. The main problem is the fact, that TIFF is not image format, but a generic envelope format. It may contain image or anything else. I see two possible solutions: - Create new MIME type application/x-tiff for TIFF container. It will contain TIFF envelope magic and it can be a subclass of both image/tiff and image/x-kodak-kdc. Only the latter two MIME types will be used as application MIME types. - Write advanced magic, which can recognize TIFF container with image/tiff and not recognize TIFF container with other data. I am not sure whether it is possible.
I think that this bug will mostly fix itself, since slowly all applications that support TIFF format start also to support raw files. The major application which is missing this feature is EOG, and there it is also work in progress (see http://bugzilla.gnome.org/show_bug.cgi?id=344601). Udi
* freedesktop.org.xml.in: Add magic for KDC Kodak raw image files * tests/list: * tests/test.kdc: Add test case for that image file (Closes: #10357)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.