Jeroen, are you sure you want to use Sylpheed? Doesn't support Quoted-Printable encoding! Btw, what's wrong with your previous MUA? Why did you switch? (You may reply privately if you are too ashamed of your previous MUA ;-) ) Maybe Sylpheed-Claws has QP support?
--- Begin Message ---
- Subject: Re: Sylpheed: Signed messages BASE64-encoded
- From: Hiroyuki Yamamoto <hiro-y@xxxxxxxxx>
- Date: Fri, 18 Oct 2002 19:08:52 +0900
Hello, On Fri, 18 Oct 2002 11:10:40 +0200 Lionel Elie Mamane <lionel@xxxxxxxxx> wrote: > Maybe the choice of Base64 makes sense for Japanese and other high-bit > rich languages, but it is a nuisance for people receiving clear signed > messages with relatively few high bit characters, and whose MUA does > not automatically decode Base64. QP encoding is better in this case, > as the message is still human-readable, even if the MUA doesn't do > QP-decoding (the encoded characters can be guessed pretty easily, as > there are few of them, and human languages are very redundant). This problem has been already realized. Using Base64 is just a quick hack. > I feel "languages with relatively few high bit characters" includes > all West European languages, and thus most (if not all) of the > ISO-8859-x character sets. > > I've prepared two patches to the src/compose.c file: > > - The first one always uses QP encoding for signed messages that > contain high-bit characters > - The second one uses Base64 for the charsets I judged would > typically have many high-bit characters. Feel free to adapt the > list. This patch won't work, because the quoted-printable encoding is not implemented yet :) Anyway, I'm going to implement it in the near future. Thanks for the bug report.
--- End Message ---
<<inline: application/pgp-signature>>