mò
d{£>c @ s d Z d d d !Z d d d !Z d d d !Z d k Z d k Z d k Z h Z d Z d Z
d
Z d Z d Z
d
Z d S( sĈ
$RCSfile: ProductProperties.py,v $
This module includes all of those properties that really belong to the
ExternalFile Product as a whole, rather than to any particular
_instance_ of ExternalFile.
These properties are loaded in from ASCII configuration files at
Zope startup time. See the comments in the top of 'mime.types'
and 'display.types' for more information.
Author: Craeg Strong
Release: 1.2
s $Name: $i iŝ˙˙˙s $Date: 2003/04/21 00:56:27 $s $Revision: 1.3 $i
Nc C s> t i | } | p d GHn | o t i i | n d S( s[
Initialize the mimetype list with addl mimetypes
from the file 'mime.types'
s% Empty or non-existent mime.types fileN( t mimetypest read_mime_typest filepatht typemapt types_mapt update( R R ( ( tM /home2/kennisonb/webapps/zope/Zope/Products/ExternalFile/ProductProperties.pyt initMimeTypeList s c C sŝ y t | } Wn t j
o d GHd Sn Xh } x¸ | i } | p Pn | i } x; t t
| D]' } | | d d j o | | 3Pqo qo W| p q8 n t
| d j o d G| d GHn | d | d } } | t |
'binary' Not editable TTW, viewed via hyperlink eg
Generally, the DisplayType is derived by parsing the type from the
mimetype. That is,
'image/jpeg' -> 'image'
'text/plain' -> 'ascii'
'application/zip -> 'binary'
In certain circumstances, this is not appropriate. For example,
'application/xml' should be 'ascii' rather than 'binary.'
t /i t imaget textt asciit binaryN( R t getR t NoneR R t typet subtype( R R+ R R* ( ( R t getDisplayTypeFromMimeTypem s
( t __doc__t
__cvstag__t __date__t __version__R t os.patht ost sysR R R R R R" R, (
R/ R R R" R R. R R R3 R, R R0 R2 ( ( R t ? s