<<< Date Index >>>     <<< Thread Index >>>

Re: Bug#222191: patch-1.4.1.tt.compat.1 for mutt fixes this bug



Hello,

On Sun, 01 Feb 2004, Thomas Roessler wrote:

> Even though I don't really like the assumed_charset feature, I'm
> somewhat tempted to adding it to mutt; I'd welcome comments on that.

I'm glad to hear that. That's really what I've wanted for years.
I don't like the assumed_charset, too. i.e. The best solution is
to tell people not to send invalid messages. But curretly I _need_ it.


> > +  { "file_charset",        DT_STR,  R_NONE, UL &FileCharset, UL 0 },
> > +  /*
> > +  ** .pp
> > +  ** [mutt-ja]
> > +  ** This variable is a colon-separated list of character encoding
> > +  ** schemes for text file attatchments.
> > +  ** If unset, $$charset value will be used instead.
> > +  ** For example, the following configuration would work for Japanese
> > +  ** text handling:
> > +  ** .pp
> > +  **   set file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"
> > +  ** .pp
> > +  ** Note: "iso-2022-*" must be put at the head of the value as shown above
> > +  ** if included.
> > +  */

Wow, you are going to implement file_charset at last!
Yes, it is reasonable to take this in to the code.
This is a bugfix of charset-handling in forwarding
encupsulated messages.

Thanks,
-- 
tamo