Re: charset conversion in text/html
The best way to solve this would probably be through a mailcap flag
that dictates whether or not a certain handler wants us to do
character set conversion on the data.
In fact, I'm just wondering what the "x-convert" flag is supposed to
do -- it's recognized by mutt's mailcap parser, but unused.
--
Thomas Roessler · Personal soap box at <http://log.does-not-exist.org/>.
On 2003-09-14 12:50:44 -0400, Alexy Khrabrov wrote:
> From: Alexy Khrabrov <braver@xxxxxxxxx>
> To: Alexy Khrabrov <braver@xxxxxxxxx>
> Cc: mutt-users@xxxxxxxx
> Date: Sun, 14 Sep 2003 12:50:44 -0400
> Subject: Re: charset conversion in text/html
> X-Spam-Level:
>
> No comments on HTML charset conversion yet:
>
> > Looks like $charset does not apply to text/html.
> >
> > Thus, one have to duplicate charset settings in
> > lynx|links|w3m|etc. Is there a way to apply
> > mutt's own conversion to text/* before handing
> > it out to the text/html MIME handler?
>
> Can somebody at confirm that's what you guys are
> doing? Say, reciving Japanese e-mail in HTML,
> or a version of Chinese?
>
> Because of it, you have to duplicate charset
> settings in the HTML dumper (dumpling?:) _and_
> in mutt. Of course, the dumpling can change,
> and it is plain tiresome. Wouldn't it be nice
> to have a config variable like
>
> auto_charset text/html
>
> a la auto_view, which will apply to those MIME
> types before passing them to auto_view?
> Then the list in auto_charset must be a subset of
> auto_view.
>
> Cheers,
> Alexy
>