Bug 397 - wmv, avi, asf files
Summary: wmv, avi, asf files
Status: RESOLVED FIXED
Alias: None
Product: shared-mime-info
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Jonathan Blandford
QA Contact:
URL:
Whiteboard:
Keywords:
: 910 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-04-01 06:48 UTC by Timo Aaltonen
Modified: 2004-11-11 09:11 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Timo Aaltonen 2004-04-01 06:48:23 UTC
Most of the wmv- and avi-files that for example I currently happen to own are in
fact asf-files, and that's why nautilus 2.6 refuses to open them (because the
content is different from suffix). I tried to add wmv and avi suffices for
ASF-mime-type, but there's no difference (but that's possibly a nautilus issue)
Comment 1 Stéphane Loeuillet 2004-05-02 23:55:22 UTC
WMA & WMV are ASF files

AVI is RIFF and is a completly different file structure (it's a RIFF, like WAV
and perhaps also MIDI files)

lots of media files on the net have the wrong extension because as windows use
extensions to associate to applications. lets not do the same mistake. we should
only rely on extension if there is no way to find the file format by looking at
magic paterns inside the file

never trust the file extension.  trust : file yourfile.dummy
Comment 2 Christian - Manny Calavera - Neumair 2004-05-15 20:38:35 UTC
http://freedesktop.org/pipermail/xdg/2004-May/003959.html
Nobody dares to review it.

regs,
 Chris
Comment 3 Timo Aaltonen 2004-05-16 00:23:12 UTC
I tried the patch, but it didn't change the behaviour..
Comment 4 Christophe Fergeau 2004-07-30 11:15:54 UTC
*** Bug 910 has been marked as a duplicate of this bug. ***
Comment 5 Timo Aaltonen 2004-11-12 04:11:01 UTC
GNOME 2.8 seems to have fixed this issue, the new MIME-system to be exact..


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.