Bug 100956 - Windows MSI installers incorectly idendified as "Microsoft Word Document"
Summary: Windows MSI installers incorectly idendified as "Microsoft Word Document"
Status: RESOLVED FIXED
Alias: None
Product: kfile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-06 11:11 UTC by David Pottage
Modified: 2018-04-11 20:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Pottage 2005-03-06 11:11:38 UTC
Version:           3.3.2 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-6)
OS:                Linux (i686) release 2.6.11

When viewing a directory in Konqueror as 'detailed file view' Windows MSI installer files are incorrectly shown as "Microsoft word"

Expected behavoir: The files should show as Microsoft installers.

Using the file command line utility (Version 4.12) the same MSI file is reported as "Microsoft Office Document", suggesting that file & Konqueror are using similar algrithoms, but that Konqueror is not simply using file to determine the file type.
Comment 1 Thiago Macieira 2005-03-06 17:34:44 UTC
Not a bug. The msi file type isn't present, so it's a wishlist to add one.

I wonder why, because you can't install them...
Comment 2 David Pottage 2005-03-06 22:50:50 UTC
If it is an unknown file type, then why is not just shown as 'Unknown' ?

To have it incorrectly identified as something else is needlessly confusing, especialy as it can be identified purley from it's file extension
Comment 3 Thiago Macieira 2005-03-07 01:39:57 UTC
It actually isn't known.

The KDE file-type matching algorithm works in two phases. One is to check the file name for matches, like *.doc or lib* (hence, no concept of "extensions").

If no match is found, we then proceed to check the file's contents. That how we can find text files that aren't named *.txt or *.log or etc.. That means we can catch a lot more files than Windows, for instance, can.

The problem here is that the content signature for Microsoft Word Documents is matching those MS Installer files. The "magic" has to be reviewed, or a file type matching *.msi has to be added.
Comment 4 David Pottage 2005-03-07 09:32:37 UTC
How easy would it be for me to make the necessary changes to the file matching magic?

My KDE system is installed from binary debian packages. Is it possible to get at the magic without installing KDE from sources? Is the format specification similar to that used by the file utility?

Where do the magic files live? where can I find a format specificaton?

If I do make the necessary changes, can I email a patch to you?
Comment 5 Allan Sandfeld 2005-03-07 10:35:40 UTC
Check what "file" detects the file as.
Comment 6 Thiago Macieira 2005-03-07 12:18:28 UTC
He's said file(1) detects it as "Microsoft Office Document".
Comment 7 Allan Sandfeld 2005-03-07 12:30:18 UTC
Sorry :)
Comment 8 Christian Loose 2005-03-07 15:01:22 UTC
If I'm not mistaken, the following should work:

1. Create a text file 'x-msi.desktop' with the following content:

[Desktop Entry]
Encoding=UTF-8
MimeType=application/x-msi
Comment=Microsoft Installer
Type=MimeType
Patterns=*.msi;*.MSI

2. Install the file in $KDEDIR/share/mimelnk/application

Comment 9 Christoph Feck 2009-08-27 02:36:09 UTC
Moving from "kio/kfile" component to "kfile" product, helps sorting out duplicates.
Comment 10 Nate Graham 2018-04-11 20:38:31 UTC
MSI is not a preinstalled known file type in KDE Frameworks 5.
Comment 11 Nate Graham 2018-04-11 20:40:11 UTC
Correction: "...is NOW a preinstalled known file type..."