[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sylpheed
Subject:    [sylpheed:25332] Re: [PATCH] do not use US-ASCII if there are
From:       Godwin Stewart <gstewart () bonivet ! net>
Date:       2005-07-09 6:09:19
Message-ID: 20050709080919.1c6d7999.gstewart () bonivet ! net
[Download RAW message or body]


On Sat, 9 Jul 2005 11:21:43 +0900, Daichi Kawahata
<daichi.k@aioros.ocn.ne.jp> wrote:

> but thinking that still I have to see broken header as well as you,
> does not the above workaround work at all? My main confusion is that
> I really don't know whether it was fault on Sylpheed or on a MUA
> sending mail with non-encoded 8bit header (at Subject, Sender).

Strictly speaking, it's the fault of the sending MUA for including 8-bit
characters in headers (which does indeed go against RFC2822) without
encoding them first of all in =?charset?[q|b]?........?= constructs.
Without such constructs, how do you know which character set was used?

You don't, and you have to guess. You can't blame sylpheed for getting it
wrong sometimes - in particular for Asian languages for which there are so
many possible character sets to choose from. I can think of 4 totally
incompatible codesets for Japanese straight away (Shift_JIS, JP_EUC, UTF-8
and ISO-2022-JP).

-- 
G. Stewart - gstewart@bonivet.net

Spotted in a toilet of a London office:
TOILET OUT OF ORDER. PLEASE USE FLOOR BELOW.

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]