I changed the application/vnd.lotus-1-2-3 magic string match to: <match offset="0" type="string" value="\x00\x00\x02\x00\x06\x04\x06\x00\x08\x00\x00\x00\x00\x00" /> according to the information on http://www.filext.com/detaillist.php?extdetail=wk1&goButton=Go I checked with a random .wk1 file I found on http://www.daniel-hertrich.de/lxgluc/ with the help of google, the magic pattern is correct. This might have fixed the problem outlined in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245262; however such .tga files are now detected as image/x-icb :-/ I'll be looking further for another solution to that problem.
About the targa || icb problem: after checking image/x-icb is in fact also listed as "Truevision Targa". Is there any reason image/x-icb is not an alias for image/x-tga, with simply .icb as an alternative glob? BTW. the magic pattern for image/x-icb is also both rather incomplete because it's too short, and inaccurate because some bytes in the pattern can have different values for a targa file, and the byte indicating it as an actual ICB targa file instead of another targa variant is not in the pattern from what I found in the targa format descriptions.
*** Bug 1733 has been marked as a duplicate of this bug. ***
I committed the lotus 123 magic stuff. I'm keeping this bug open and retitling it for the tga issue.
Thanks for your bug report! I've merged ICB into the TGA MIME type, and added some more extensions. According to [1], there exist some TGA flavors. [1] http://netghost.narod.ru/gff/graphics/summary/tga.htm
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.