From fc68923b1110d26c8d5185adaa701dd9a34991fa Mon Sep 17 00:00:00 2001 From: Dan Winship Date: Wed, 30 May 2001 22:05:36 +0000 Subject: Use the config-specified default character set (which in turn defaults to * e-msg-composer.c (build_message): Use the config-specified default character set (which in turn defaults to the locale character set) as the default for encoding non-US-ASCII messages, assuming it works. Fall back to camel_charset_best() if it fails. Also, pick the Content-Transfer-Encoding based on how the data looks in the destination charset, not in UTF8. While I was here, I also refactored a bunch and tried to reduce redundant code. There are still too many places that set the transfer-encoding on the plaintext part though... Also, I think some more cleanliness could happen if the sign/encrypt interfaces returned CamelMultiparts instead of CamelMimeParts. svn path=/trunk/; revision=10058 --- composer/ChangeLog | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'composer/ChangeLog') diff --git a/composer/ChangeLog b/composer/ChangeLog index e771a2e03a..39ea911219 100644 --- a/composer/ChangeLog +++ b/composer/ChangeLog @@ -1,3 +1,18 @@ +2001-05-30 Dan Winship + + * e-msg-composer.c (build_message): Use the config-specified + default character set (which in turn defaults to the locale + character set) as the default for encoding non-US-ASCII messages, + assuming it works. Fall back to camel_charset_best() if it fails. + Also, pick the Content-Transfer-Encoding based on how the data + looks in the destination charset, not in UTF8. + + While I was here, I also refactored a bunch and tried to reduce + redundant code. There are still too many places that set the + transfer-encoding on the plaintext part though... Also, I think + some more cleanliness could happen if the sign/encrypt interfaces + returned CamelMultiparts instead of CamelMimeParts. + 2001-05-28 Jeffrey Stedfast * e-msg-composer-attachment-bar.c (update): Use -- cgit