[sylpheed:32874] Re: problem with quoted-printable encoding and charset iso-8859-1

[Celejar]

On Fri, 20 Feb 2009 23:05:36 +0200
Cristian Secară <orice at secarica.ro> wrote:

> On Fri, 20 Feb 2009 14:10:41 -0500, Celejar wrote:
> 
> > I'm receiving mail with these MIME headers:
> > Content-type: text/plain; charset=iso-8859-1; format=flowed
> > Content-transfer-encoding: quoted-printable
> > [...]
> > The text contains '=20' at the end of every line, which is legitimate
> > ('space'), but it also contains scattered '=92', '=93' and '=94'.
> > Sylpheed (2.5.0 on Debian) shows the 'unprintable' box glyphs for
> > these, apparently because those numbers are undefined in 8859:
> 
> These characters (’, “ and ”) are coming from Windows CP1252 8 bit
> proprietary encoding and they cannot exist under ISO-8859-1.
> 
> > Am interpreting all this correctly?  Is the sending mailer just broken
> > and sending bad mail?
> 
> It appears yes, the program should warn about the impossible
> encoding in the given conditions and offer to switch the encoding as
> Unicode instead (or ask the user to correct its text, but it is
> unlikely that an average user knows exactly what the precise problem
> is).

Just in case anyone has any use for this, I'm posting a little procmail
type filter written in perl that checks if a message has been sent by
Windows Eudora (or any other arbitrary mailer), and if so, replaces the
charset, if iso-8859-1, by windows-1252.

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator

-------------- next part --------------
A non-text attachment was scrubbed...
Name: eudora-correct.pl
Type: text/x-perl
Size: 1376 bytes
Desc: not available
Url : http://www.sraoss.jp/pipermail/sylpheed/attachments/20090224/be7af64a/attachment.bin