Mime types - uppercase appearing in mime type names
thomas at kluyver.me.uk
Mon Mar 18 07:22:35 PDT 2013
I've filed a bug about this:
It's against xdgmime, as there doesn't seem to be a component for the
shared-mime-info spec. It would need both a (small) spec change and a code
On 15 March 2013 23:22, Jerome Leclanche <adys.wh at gmail.com> wrote:
> Agreed. If the files are not lowercase, we could have conflicts (which we
> actually do as you mentioned).
> J. Leclanche
> On Fri, Mar 15, 2013 at 10:11 PM, Thomas Kluyver <thomas at kluyver.me.uk>wrote:
>> Almost all Mime types are named in lower case, e.g. image/png. However,
>> there are a handful of MS office file formats that the freedesktop.orgdatabase uses the word 'macroEnabled', e.g.
>> The same type is also defined by LibreOffice, but in lowercase, i.e.
>> I also see uppercase in audio/AMR, audio/AMR-WB and text/x-iMelody.
>> RFC 2045  says "The type, subtype, and parameter names are not case
>> sensitive." I can flatten the case easily enough, but looking up the
>> MEDIA/SUBTYPE.xml files on a case-sensitive filesystem gets tricky - I
>> would have to keep a reference to the original spelling, just for those few
>> To simplify this, I think the shared mime-info spec should say that the
>> media/subtype.xml files are always named in lowercase. Since the names are
>> supposed to be case insensitive, it shouldn't create conflicts.
>> update-mime-database should also merge mimetypes regardless of case - at
>> present, I see separate media/subtype.xml files for the 'macroEnabled' and
>> 'macroenabled' mimetypes.
>>  http://tools.ietf.org/html/rfc2045
>> xdg mailing list
>> xdg at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the xdg