FWIW, even Thunderbird doesn't handle multi-byte characters split across
multiple encoded-word tokens. I was just checking out their
implementation in
mozilla/netwerk/src/nsMIMEHeaderParamImpl.cpp:DecodeRFC2047Str()
Jeff
On Sun, 2007-12-23 at 23:09 +0800, jacky wrote:
> Hi, all.
>
> The rfc204
Hi Jacky,
I've looked over your patch, but unfortunately it is unusable. The patch
is riddled with buffer overflows and incorrect logic.
What types of bugs are you actually trying to fix? What is it about CJK
messages in particular that are not getting decoded properly? Your email
was overly vagu
--- Philip Van Hoof <[EMAIL PROTECTED]>wrote:
> Hey Jacky,
>
> This is a port of your patch to Tinymail's
> camel-lite
>
Thank you.
> On Sun, 2007-12-23 at 23:09 +0800, jacky wrote:
> > Hi, all.
> >
> > The rfc2047 decoder in libcamel can not decode
> some
> > CJK header correctly. Although
Hey Jacky,
This is a port of your patch to Tinymail's camel-lite
On Sun, 2007-12-23 at 23:09 +0800, jacky wrote:
> Hi, all.
>
> The rfc2047 decoder in libcamel can not decode some
> CJK header correctly. Although some of them are not
> correspond to RFC, but I need to decode it correctly
> and I
Hi, all.
The rfc2047 decoder in libcamel can not decode some
CJK header correctly. Although some of them are not
correspond to RFC, but I need to decode it correctly
and I thought if evolution can display there email
correctly more people like it.
So I write a new rfc2047 decoder, and it's in the
