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 --On Sonntag, 8. Juli 2001 09:47 -0500 Andreas Jung <andreas@andreas-jung.com> wrote:

Please put it in the collector and we will add it.

Andreas ----- Original Message ----- From: "Robert Rottermann" <robert@redcor.ch> To: <zope@zope.org> Sent: Sonntag, 8. Juli 2001 08:35 Subject: [Zope] Missing mime-types

...

Hi there, I am implementing a facility to have DWG-files as content in CMF. Checking the OFS\content_types.py I find "application/acad" and "application/dxf" missing.

According to what filter was the list of mime types selected ? Would it be possible to add the two above mentioned types?

Robert

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )

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 `------------------>

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 `------------------>

From: "marc lindahl" <marc@bowery.com> To: <zope@zope.org> Sent: Montag, 9. Juli 2001 10:38 Subject: Re: [Zope] Missing mime-types

What about the issue of, a Product developer makes a product designed to deal with some new mimetype... proper operation depends on recognition of this mimetype. Should content_types.py expose the interface to globally add a new type?

This can be accomplished on the mimetypes.py level - or ?! Andreas