Re: [evolution-patches] header decoding patch

[Jeffrey Stedfast <fejj ximian com>]

Because it's a work-around for broken mailers that rfc2047 encode the Content-Type/Content-Disposition parameters.

Jeff

On Mon, 2004-03-29 at 23:43 +0800, Not Zed wrote:

> uh, so why does the code ust rfc 2047 decoding?
>
> >From what i can read ... "two or more 2047 encoded words" is more
> accurate than using "words", which have ZER0 I18N capability.
>
> On Mon, 2004-03-29 at 09:18 -0500, Jeffrey Stedfast wrote:
> > Sure, although this is just a workaround for broken mailers. It is
> > illegal to encode parameters like this using the rules in rfc2047.
> > Mailers are supposed to be using rfc2231 (or its predecessor, rfc2184).
> > 
> > Jeff
> > 
> > On Mon, 2004-03-29 at 04:58, Andrei Nigmatulin wrote:
> > > Hello,
> > > 
> > > This patch fixes incorrect decoding of attachment filename.
> > > If filename specified in Content-Disposition header is made
> > > of two or more "encoded words" (in terms of rfc2047)
> > > then mailer try to decode such filename as it was one "encoded word".
> > -- 
> > Jeffrey Stedfast
> > Evolution Hacker - Ximian, Inc.
> > fejj ximian com  - www.ximian.com
> > 
> > _______________________________________________
> > Evolution-patches mailing list
> > Evolution-patches lists ximian com
> > http://lists.ximian.com/mailman/listinfo/evolution-patches