I disagree. The handling of mime-types happens first on the Python level. mimetypes.py comes with four hardcoded locations where it looks for mime.types files (no support for windows). User-defined mime-types should be put into a local mime.types file. The most common mime-types should be part of the mimetypes module and there should be some additional support in the mimetypes module to specify user-defined mime.types file (env.var or any other mechanism). But it makes few sense to maintain the mime-types at at-least three different locations (Zope, Python, local mime.types files). Andreas ----- Original Message ----- From: "Casey Duncan" <cduncan@kaivo.com> To: "Tino Wildenhain" <tino@wildenhain.de> Cc: "Andreas Jung" <andreas@andreas-jung.com>; "Robert Rottermann" <robert@redcor.ch>; <zope@zope.org> Sent: Montag, 9. Juli 2001 10:03 Subject: Re: [Zope] Missing mime-types
Tino Wildenhain wrote:
Hi,
this cries for a proposal for an extending mechanism rather then announcing all future and custom mime-types to the collector ;)
(Not to mention creating objects based on the mime-type)
Regards Tino
This could probably be patched pretty readily by a hotfix without changing Zope core code.
Ultimately it might be nice to just put them into a text file that users can add to. Or possibly multiple text files to prevent overwrites when you upgrade Zope.
-- | Casey Duncan | Kaivo, Inc. | cduncan@kaivo.com `------------------>