Bug 364

Summary:	More ImageMagick types
Product:	shared-mime-info	Reporter:	Thomas Leonard <tal00r>
Component:	freedesktop.org.xml	Assignee:	Jonathan Blandford <jrb>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	high	CC:	bugzilla, daniel.leidert.spam
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Extra types

Description Thomas Leonard 2004-03-23 06:30:46 UTC

From xdg list post by Guido Schimmels. The first set were already applied, but
the second set might need more checking. Adding it here so as not to forget...

Original email:

ImageMagick supports a number of types not yet in the fd.o database.
I tried to add those by help of http://filext.com. I don't know of a
better source. IANA web resources weren't helpfull.
                                                                                
magick1.xml has types which had a mime-type submitted to
http://filext.com. Although in almost all cases there were a bunch to
choose from.
                                                                                
magick2.xml has types for which I couldn't find a reference, so I
created this file to the best of my understanding.
                                                                                
I need those types added, so they can be thumbnailed in ROX-Filer.
Without those types in the database the respective plugins can't be
used.

Comment 1 Thomas Leonard 2004-03-23 06:31:25 UTC

Created attachment 165 [details] [review]
Extra types

Comment 2 Abel Cheung 2005-02-12 15:21:52 UTC

ping?

Some files types listed in the patch, such as .miff (native image type used in
ImageMagick), .wbm (Wireless bitmap) etc are already widely accepted in
public, though probably not into IANA yet.

Comment 3 Bastien Nocera 2006-07-09 02:59:44 UTC

Comment on attachment 165 [details] [review]
Extra types

><?xml version="1.0"?>
><mime-info xmlns='http://www.freedesktop.org/standards/shared-mime-info'>

Don't make a separate file out of those types, they should be integrated in
freedesktop.org.xml.in

>  <mime-type type="application/x-1st-puplisher-art">
>	<comment>First Publisher ART file</comment>

mark those as translatable (_comment instead of comment)

>  </mime-type>
>  <mime-type type="application/x-stardent-avs">
>	<comment>Stardent AVS X image</comment>

You need to use acronym and expanded-acronym when you have acronyms in your
type names.

>	<glob pattern="*.avs"/>
>  </mime-type>
>  <mime-type type="image/x-cmyk">
>    <comment>Raw Cyan, Magenta, Yellow, and Black samples</comment>

Bit long comment?

<snip>
>  <mime-type type="video/mpeg2-video">
>	<comment>MPEG-2 video only file</comment>
>	<glob pattern="*.m2v"/>
>  </mime-type>

That's most definitely wrong.

<snip>
>  <mime-type type="image/uyvy">
>	<comment>interleaved YUV raw image</comment>
>	<glob pattern="*.uyvy"/>

That sounds like a bizarre extension and mime-type that seems to spell
"Uninterleaved YVY".

>  </mime-type>
>  <mime-type type="image/vicar">

If the mime-type has no x-, it should be an IANA mime-type. Have a reference?

<snip>
>  <mime-type type="image/wbm">

Same.

>	<comment>Wireless bitmap</comment>
>	<glob pattern="*.wbm"/>
>  </mime-type>
>  <mime-type type="image/yuv">
>	<comment>CCIR 601 image</comment>
>	<glob pattern="*.yuv"/>

That looks mighty unusual as well.

Comment 4 Bastien Nocera 2008-06-11 09:56:32 UTC

Patch hasn't been updated in 2 years, closing.

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.