Re: [evolution-patches] header decoding patch

[Jeffrey Stedfast <fejj ximian com>]

On Mon, 2004-03-29 at 20:31 +0400, Andrei Nigmatulin wrote:

> > 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...

When I wrote the workaround, I had only ever encountered single rfc2047 encoded-word tokens in param value qstrings and so I didn't bother using header_decode_text() since for all examples it wouldn't have been necessary.

That said, I applied your patch to 1.5 CVS

Jeff

> --
> Andrei Nigmatulin
> _______________________________________________
> Evolution-patches mailing list
> Evolution-patches lists ximian com
> http://lists.ximian.com/mailman/listinfo/evolution-patches