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

0 files changed, 0 insertions, 0 deletions