[mew-int 01393] Re: StarSuite

[Kazu Yamamoto ( 山本和彦 )]

From: "clemens fischer" <ino-qc at example.com>
Subject: [mew-int 01380] Re: StarSuite

> so on unix, would this program be responsible for mapping
> Content-Type to an actual program, like metamail used to do according
> to ~/.mailcap (and a little ~/.mime.types)?

mew-mime-content-type of Mew is .mailcap of metamail.

> so mew contains a table somewhere mapping Content-* headers to
> suffixes.  is this a documented variable users can change?

The suffix of a temporary file, which is passed to an external
program, is determined accroding to the Content-Disposition:
field. Optionally, if mew-use-name-paramete is non nil, the *illegal*
NAME parameter in the Content-Type: field is also used.

> so there must be a table connecting the
> two.  is this an open table?

Yes. But this table should be shared by all Mew users. If you want to
add new entry for a new Content-Type:, please propose it on this ml.
It should be included in the next release.

The document of mew-mime-content-type was poor. So, I have written
comprehensive document and committed to anon cvs.

> my problem with this is:  how can i specify new MIME types by setting
> CT:?  i know i could make up custom MIME types easily if there was a
> table.

Use the mew-insert-after macro to add an entry to
mew-mime-content-type.

But again, such entries should be shared by all Mew users.

--Kazu