Re: Inconsistency between mime-support, shared-mime-info and file for PHP files media types.
- To: firstname.lastname@example.org
- Subject: Re: Inconsistency between mime-support, shared-mime-info and file for PHP files media types.
- From: Charles Plessy <email@example.com>
- Date: Sat, 1 Sep 2012 09:54:10 +0900
- Message-id: <20120901005410.GA21604@falafel.plessy.net>
- In-reply-to: <firstname.lastname@example.org>
- References: <20120824140448.GC18069@falafel.plessy.net> <5037AD96.email@example.com> <CALjhHG8ukz9UjN-AC7LkJBY_cLCbxBWC93Zw1DOhTwznx6Jf3A@mail.gmail.com> <1345902277.8842.20.camel@deep-thought> <firstname.lastname@example.org> <email@example.com> <20120829221641.GB2556@falafel.plessy.net> <firstname.lastname@example.org> <1346312226.3479.310.camel@pi0307572> <email@example.com>
Le Thu, Aug 30, 2012 at 12:48:01AM -0700, Russ Allbery a écrit :
> That's the reason why people are pursuing generating the metamail-style
> database *from* the XDG MIME specification so that we can use a richer
> specification in as many places as possible but fall back on the previous
> standard for applications that still use it.
I would be interested to have pointers to such projects.
For the registered media types, in my undestanding both mime-support (or its
equivalents in other distributions) and shared-mime-info (through its XDG
upstream) are tracking IANA's definitions, which is a duplication of work that
I would be glad to see resolved. The biggest hurdle is probably that the
divergence in regard to the unregistered types, and the potential side effects
of changes if a merger happened.
Have a nice week-end,