After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 342800 - MIME type by content, not file name extension
MIME type by content, not file name extension
Status: RESOLVED DUPLICATE of bug 336448
Product: evince
Classification: Core
Component: general
0.5.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-24 11:52 UTC by Jan "Yenya" Kasprzak
Modified: 2006-05-24 15:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Jan "Yenya" Kasprzak 2006-05-24 11:52:50 UTC
When I download a PDF or PostScript file from the web, the browser often saves
the file as <something>.cgi (or .pl or .php or whatever), based on the URL of the application, which generated the document. Such document then cannot be displayed by evince, because it thinks that it has "application/x-perl" (or similar) MIME type. I think evince should determine the MIME type of the local file based on the file contents, not extension (using for example the shared-mime-info package). All other viewers/file readers I know of (eog, gthumb, gimp, xmms, mplayer ...)
ignore the file name/extension, and use the file contents instead. I believe evince should do the same.
Comment 1 Nickolay V. Shmyrev 2006-05-24 11:59:29 UTC
This problem should be fixed in recent CVS. Please check. Although there are some reports that it doesn't work still. Anyhow, let's discuss this problem in original bug.

*** This bug has been marked as a duplicate of 336448 ***
Comment 2 Jan "Yenya" Kasprzak 2006-05-24 15:58:10 UTC
It seems this bug is still present in today's CVS version (I will add the same comment to the bug #336448).