Re: [Evolution-hackers] [patch] fixed incorrect rfc2047 decode for CJKheader



--- jacky <gtkdict yahoo com cn>worte:

> 
> --- Peter Volkov <pva gentoo org>wrote:
> 
> > 
> > В Пнд, 24/12/2007 в 13:21 +0800, jacky
> > пишет:
> > > --- Jeff Stedfast <fejj novell com>wrote:
> > > There are two kind of email need to support:
> > > 1) An encoded-word was divided into two line.
> This
> > was
> > > sent by dotProject v2.0.1 .
> > 
> > And there are even more users affected by this.
> I've
> > already reported
> > similar problem in bug 315513. Thus this affects
> not
> > only CJK people:
> > 
> > http://bugzilla.gnome.org/show_bug.cgi?id=315513
> > 
> 
> In fact, the parser and decoder in my patch support
> this encoded-words. I already mentioned in my email:
> > 2) A CJK character's encoded string must in an
> > encoded-word, but some email client divide it into
> two
> > encoded-words.
> 
> But the problem describe below has not been solved.
> > 1) An encoded-word was divided into two line. This
> was
> > sent by dotProject v2.0.1 .
> 
> As I seen this kind of email use quoted encode only,
> and header_decode_text() can get all encoded-words
> which is separated by SPACE, a simple solution is

CORRECTION:
header_decode_text() can get whole encoded-word
which is separated by SPACE
Sorry for my poor English. 
An example:
=?utf-8?Q?=E7=B3=BB=E7=BB=9F=E7=A0=94=E7=A9=B6<break>
=E5=B7=B2=E6=9B=B4=E6=96=B0?=

> replace SPACE with '_'. In fact OpenWebmail do like
> this. 
> But the problem is I must change the prototype of
> header_decode_text() to 
> char *header_decode_text (char *in, size_t inlen,
> int
> ctext, const char *default_charset)
> Originality, it is
> char *header_decode_text (const char *in, size_t
> inlen, int ctext, const char *default_charset)
> Functions which call header_decode_text() must been
> changed too.
> Does anyone have better proposal?
> 
> > -- 
> > Peter.
> > 
> 


      ___________________________________________________________ 
雅虎邮箱传递新年祝福,个性贺卡送亲朋! 
http://cn.mail.yahoo.com/gc/index.html?entry=5&souce=mail_mailletter_tagline


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]