Hi, I see no use for mime-type files who match file extensions to mime types in a world without file extensions :) (let allone wrong file extensions) If the mime-type definitions allow some code or even simple pattern matching at the beginning of the files, the use would be better. Unfortunately this does not help the somewhat silly mime-type handling in zope, or Folder, precisely. Regards Tino --On Montag, 9. Juli 2001 09:29 -0600 Casey Duncan <cduncan@kaivo.com> wrote:
Andreas Jung wrote:
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).
Actually what I was saying was that there should be two files containing all MIME-types and none would be hard-coded. One would come with Zope and another could be added by a user if they wanted to support additional ones.
However since it seems that support for a list in a file is already there (except for Windows), there doesn't seem to be a strong need to change things. Perhaps just making it support Windows would help...
-- | Casey Duncan | Kaivo, Inc. | cduncan@kaivo.com `------------------>