Re: [evolution-patches] header decoding patch

[Andrei Nigmatulin <nigmatulin_a incom-mcbn ru>]

> If you are going to quote an RFC for me, at least quote the CORRECT
> RFC. Content-Type and Content-Disposition parameter values are
> supposed to be encoded using the rules specified within rfc2231 (or,
> it's predecessor, rfc2184) as they CANNOT be encoded using rfc2047
> (the syntaxes clash).

Okay, thank you for detailed explanations. Now I see you're exactly right.
But why code mentioned does rfc2047 decoding at all? If, as you've said
"this is workaround for broken mailers", why do not include COMPLETE
workaround ? Is broken workaround better than its absence ? I see no
logic here...

--
Andrei Nigmatulin