An old precedent is the way the IBM 'Web Explorer' did it: A file whose format is 'mime/type extension_list'
The full path to this file might be specified by an item in the os2.ini entry: <application:Mozilla> <key:extmap> Alternatively, its full path might be specified in a new environmental variable EXTMAP, with a default %ETC%\extmap But there used to be a file called mailcap whose format was 'mime/type; program_name params'. The functions of this file have been taken over by by the 'Helper Applications' panel within 'Preferences'. And the entries in this panel ALREADY declare the applicable extensions (even though Mozilla/2 in its current state apparently does not *look* at these extension names). Why not "beef up" scanning of the entries in the 'Helper Applications' panel (to __look at__ extension names) ? That would take advantage of the already-existing capability for adding/editing "Helper Application' entries. (Isn't that what at least one of the Netscape/2 versions did?) mikus On Wed, 27 Mar 2002 17:08:20 -0600 Michael Kaply <[EMAIL PROTECTED]> wrote: > We need a way to map some default mime types to extensions in OS/2, > similar to a mime.types file on Linux or the registry on Windows. > > We have a couple ways to do this, and I need some opinions. > > 1. Actually use a mime.types files. This would be a text based file that > stored the extensions. The location of the file would be specified as a > preference. > > 2. Create an INI file in OS/2 (like MIMETYPE.INI or something silly) > that stored extension to mime type mappings. > > 3. Create a Mime Types entry in OS/2 ini that had all the extensions and > a corresponding mime type. > > Note that options 1 and 3 only store extension to mime type mapping > whereas number 2 could actually store additional info like a default > application to start the mime type with. > > What do people think is best?
