[Debichem-devel] Bug#420795: chemical-mime-data: Unknown media type in type 'chemical/x-*'

[Daniel Leidert]

Am Sonntag, den 28.03.2010, 11:53 +0200 schrieb Petter Reinholdtsen:
> [Daniel Leidert]
> > That's absolutely ok. It is a different
> > situation. update-mime-database complains about the unregistered
> > 'chemical' media type, not about the an unregistered MIME type (it
> > doesn't know, which MIME types have been registered - but it knows
> > the registered media types, which have been proposed in the
> > MIME-RFCs. 'chemical' has never been registered, so it does complain
> > about all MIME types with this media type. Ditto for e.g.  'fonts'
> > in fonts/package or 'all' in 'all/allfiles'. That's why u-m-d
> > complains.
> 
> I still fail to understand how application/x-oregano is different from
> for example chemical/x-alchemy.

'application' has been registered, but 'chemical' has not. u-m-d
complains about the primary part of the MIME type: 'chemical',
independent from the specific sub-type. application, text, video, ...
are all registered primary types. 'chemical' has been proposed as
primary type in 1995/96, but has never been registered. u-m-d registers
the know primary (or media) types in const media_types and because
'chemical' is not part of it, it complains about the *primary/media*
type in get_type(). This is what you see on your screen.

To get back to your example: application/x-oregano is an unregistered
MIME type (that JFTR follows the RFC - the 'x-' indicates an
unregistered sub-type) with a valid primary type. That's why u-m-d does
not complain. chemical/pdb is also an unregistered MIME type, but with
an unregistered primary type. So u-m-d complains.

Do you understand know?

Regards, Daniel