On Friday, April 28, 2006 at 10:54:17 +0400, Dmitry E. Oboukhov wrote:
> On 12:24 Thu 27 Apr , Alain Bench wrote:
>> The $rfc2047_parameters setting is relevant to attachment filename
>> decoding, not to subject.
> And why is it not relevant for subject?
All hi-bit subjects are (or should be) RFC2047 encoded. So Mutt
always decodes 2047 subjects: A setting to disable this wouldn't make
much sense.
> According to this RFC http://www.faqs.org/rfcs/rfc2047.html it can be
> applied to any message header, isn't it?
Not all: RFC 2047 itself explicitly prohibits RFC 2047 encoding in
some headers or part of headers. See chapter #5. Example: The parameters
of the "Content-Disposition:" field MUST NOT use encoded words. The
"filename=blah.dat" of an attachment is such a parameter.
> However Mutt shows the mails, which have in their bodies/attaches
> print-quoted format with spaces, correctly.
What do you mean exactly? Don't confuse body and header: Spaces are
allowed in QP body parts.
> I'll use Your patch, thank You. :-\
You're welcome.
BTW something munged the format of your reply, especially quotes.
What happened?
Bye! Alain.
--
set honor_followup_to=yes in muttrc is the default value, and makes your
list replies go where the original author wanted them to go: Only to the
list, or with a private copy.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
