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 <[email protected]>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. > > application/vnd.ms-excel.sheet.macroEnabled.12 > > The same type is also defined by LibreOffice, but in lowercase, i.e. > macroenabled. > > I also see uppercase in audio/AMR, audio/AMR-WB and text/x-iMelody. > > RFC 2045 [1] 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 > cases. > > 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. > > Thanks, > Thomas > > [1] http://tools.ietf.org/html/rfc2045 > > _______________________________________________ > xdg mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/xdg > >
_______________________________________________ xdg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xdg
