Re: [Evolution] title encoding

[Not Zed <notzed ximian com>]

On Wed, 2004-06-16 at 14:52 +0200, Xavier Bestel wrote:
> On Wed, 2004-06-16 at 08:29 -0400, Jeffrey Stedfast wrote:
> > On Wed, 2004-06-16 at 14:21 +0200, Xavier Bestel wrote:
> > > On Wed, 2004-06-16 at 18:12 +0800, Not Zed wrote:
> > > > The string can't contain any spaces, including linear white space.
> > > > The whole token is supposed to be less than 76 characters  for this
> > > > purpose, so that any folding (wrapping on multiple lines) is outside
> > > > the token boundaries.
> > > 
> > > Ok. I also have this one, which doesn't contain whitespace in the
> > > encoded part:
> > > 
> > > Subject: d=?ISO-8859-1?B?6Q==?=claration assurance
> > > 
> > > And it's still not decoded by Evo.
> > 
> > an 'encoded-word' is defined to be tokenisable as an rfc0822 'word'
> > token, of which this is not - it is instead embedded into the middle of
> > an rfc0822 word.
>
> I see. Braindamaged sender mailer, indeed.
The rfc also says that encoded words MUST be surrounded by whitespace, etc etc.
> Any chance for Evo to workaround this (mainly from Outlook for Mac, but
> also various web mailers), or will this complicate the parser too much ?

This was discussed previously, at least this second case.  Someone worked on a patch but unfortunately the workaround isn't trivial (its not super hard, but we're busy).

Still, i'm extremely loathe to, since it is a clear breakage of a pretty simple set of rules from a not-particularly complex rfc.  Seriously, MS should know better, for such a fundamental issue.  We've had issues with rfc compliance in that code and fixed it, i'm sure they can too.

--

Michael Zucchi <notzed ximian com> Ximian Evolution and Free Software Developer