[sylpheed:30744] Re: missing encoding protection in case of impossible encoding in header fields

[Hiroyuki Yamamoto]

Hello,

On Tue, 16 Jan 2007 21:52:30 +0200
Cristian Secară <orice at secarica.ro> wrote:

> When using an encoding different than UTF-8, if I enter some language
> specific characters that does not belong to the selected codepage, an
> error popup asks me if I want to send the body as UTF-8 instead.
> However, nobody prevent me to send the message if my
> particular character(s) are in the To:, From:, Subject, Cc: etc.
> fields.
> 
> For example, my name is Secară. If I choose ISO-8859-1 encoding, the
> "ă" character cannot be encoded, but for some reason Sylpheed does not
> notify that and it send it with an nonsense encoding.
> 
> In my example the encoding is this
> =?ISO-8859-1?Q?Secar=5F=5F?=
> and the displayed name is this
> Secar__

Confirmed. I'll fix it.

-- 
Hiroyuki Yamamoto <hiro-y at kcn.ne.jp>