commit: horde/config mime_drivers.php.dist mime_mapping.php.dist
horde/docs CHANGES horde/lib/MIME Magic.php Viewer.php
horde/lib/MIME/Viewer default.php enscript.php php.php
avsm@horde.org
avsm@horde.org
15 Apr 2001 23:38:03 -0000
avsm 2001/04/15 16:38:03 PDT
Modified files:
docs CHANGES
Added files:
config mime_drivers.php.dist
mime_mapping.php.dist
lib/MIME Magic.php Viewer.php
lib/MIME/Viewer default.php enscript.php php.php
Log:
Here we go! An experimental new framework to render any input file
into any output format. It consists of:
- MIME_Magic: currently takes a file extension and maps it onto
a MIME type. If a useful MIME type cannot be determined, then
it maps onto a special x-extension/* namespace, which can be used
as a normal MIME type by the rest of the framework.
- MIME_Viewer: a factory class which accepts a MIME_Part object, and
returns a subclass which is capable of rendering the object.
- MIME_Viewer_php: this handles any PHP source code, and invokes the
internal PHP routines to syntax-highlight it
- MIME_Viewer_enscript: GNU enscript pretty-print driver
- MIME_Viewer_default: A pass-through if we don't have any other drivers
There are two new configuration files:
mime_mapping.php - Apache uses a mime.types file to determine a MIME
type for common extensions. However, we want web-server independence,
and give users the ability to extend the extension -> MIME mapping
for themselves if they desire. There is a script in scripts/mime_mapping
which can sync the Apache mime.types file with a mime_mapping.php
configuration file in PHP format. This also saves us the trouble
of opening and parsing the mime.types file every single time.
mime_drivers.php - The configuration file for the drivers. Commented.
Revision Changes Path
1.132 +3 -0 horde/docs/CHANGES