[sylpheed:32880] unicode-1-1-utf-7 question

Marc Finet m.dreadlock at gmail.com
Wed Mar 4 08:13:36 JST 2009


I'm a sylpheed user for a little while and just discovered a mail
that was treated strangely by sylpheed (see attached 29 file), i.e.
not rendering utf7 (i didn't check it was correct utf-7) like '+AOk-'
as i expected 'é'. Well i'm not used to encodings so it might not
appear good, it's just the accented 'e'.

The problem seems to come from unicode-1-1-utf7 encoding format, as
seen in file/mail. It appears "inline" as =?unicode-1-1-utf-7?... or
in charset=unicode-1-1-utf-7. I'm definitely not familiar with mail
RFCs and norms and what i quickly saw in sylpheed's code (2.6.0 on
gentoo) told me that UTF_7 seems to be defined (CS_UTF_7) so i guessed

Now my questions are:
 - is this mail valid ? (RFC regarding such encoding as google told
me is rfc1642) ? otherwise i will 'complain' about sender (I didn't
check yet sender user-agent) and none of my following question have
 - is sylpheed compliant with this RFC ?
 - is sylpheed compliant with utf-7 ?
 - what could be done (i could give some help; i'm just a
C-developer but interested in lending a hand, given a few hints on
work to be done, i.e. utf-7 support first, then unicode-1-1-utf7 as
an alias or something like that...) ? 

Many thanks,


PS: googling unicode-1-1-utf-7 leads to post on python for such an
alias to utf7 but doesn't come to 'bug' page, just mailing list post.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 29
Type: application/octet-stream
Size: 4038 bytes
Desc: not available
Url : http://www.sraoss.jp/pipermail/sylpheed/attachments/20090304/9b7eff85/attachment.obj 

More information about the Sylpheed mailing list