[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mutt-dev
Subject:    Re: Decoding of attachment filenames
From:       Will Fiveash <will () austin ! ibm ! com>
Date:       2000-01-29 17:49:04
[Download RAW message or body]

Thomas and Mikko,

Thanks for the updated docs concerning RCF2047 decoding.  Thomas, if you
are so inclined please feel free to use or modify any of my previous
comments on your doc when updating the mutt manual.  

Perhaps in the future, additions to the mutt manual should be reviewed on
either the mutt-dev or mutt-users list and people could make editorial
suggestions.  This could go a long way towards making the docs more
meaningful to a wider audience. 

On Sat, Jan 29, 2000 at 08:27:39AM +0100, Thomas Roessler wrote:
> On 2000-01-28 17:51:26 -0600, Will Fiveash wrote:
> 
> > <Thomas, are you saying the user must use the 'c'hange folder
> > command before mutt will use RFC2047 decoding?>
> 
> Technically, the setting only applies on any MIME parameters which
> are parsed after it has been changed.  This means that, before
> re-parsing the entire folder, users will get a confusing mix of
> encoded and decoded parameters, depending on whether or not they are
> looking at multiparts, and whether or not they have seen that
> message before.

Okay, perhaps you could add the above to the docs?

-- 
Will Fiveash

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic