aboutsummaryrefslogtreecommitdiffstats
path: root/composer/ChangeLog
diff options
context:
space:
mode:
authorJeffrey Stedfast <fejj@ximian.com>2002-07-23 07:34:34 +0800
committerJeffrey Stedfast <fejj@src.gnome.org>2002-07-23 07:34:34 +0800
commit26524d4a05dc4bb8cde52f7ca52d4e8af4e9b717 (patch)
tree82d799fbfc8cb9ec3c37eb82e326548ab714571b /composer/ChangeLog
parent6e0ef227eeba9219ad5e49afd6f9d3dbb31ecf39 (diff)
downloadgsoc2013-evolution-26524d4a05dc4bb8cde52f7ca52d4e8af4e9b717.tar
gsoc2013-evolution-26524d4a05dc4bb8cde52f7ca52d4e8af4e9b717.tar.gz
gsoc2013-evolution-26524d4a05dc4bb8cde52f7ca52d4e8af4e9b717.tar.bz2
gsoc2013-evolution-26524d4a05dc4bb8cde52f7ca52d4e8af4e9b717.tar.lz
gsoc2013-evolution-26524d4a05dc4bb8cde52f7ca52d4e8af4e9b717.tar.xz
gsoc2013-evolution-26524d4a05dc4bb8cde52f7ca52d4e8af4e9b717.tar.zst
gsoc2013-evolution-26524d4a05dc4bb8cde52f7ca52d4e8af4e9b717.zip
Removed a lot of extra g_return_if_fail's that we don't need (if we are
2002-07-22 Jeffrey Stedfast <fejj@ximian.com> * e-msg-composer.c: Removed a lot of extra g_return_if_fail's that we don't need (if we are going to check if the pointer is a a composer widget using the gtk type-check macros, then there is no need to first check that it isn't NULL). (get_file_content): Signatures are now supposed to be in UTF-8 and not the user's locale charset, so we must first read in the content, then check that it is valid UTF-8. If it isn't, then we need to try to convert it to UTF-8. svn path=/trunk/; revision=17538
Diffstat (limited to 'composer/ChangeLog')
-rw-r--r--composer/ChangeLog4
1 files changed, 4 insertions, 0 deletions
diff --git a/composer/ChangeLog b/composer/ChangeLog
index 0fb25d1c2f..24241afd81 100644
--- a/composer/ChangeLog
+++ b/composer/ChangeLog
@@ -4,6 +4,10 @@
we don't need (if we are going to check if the pointer is a a
composer widget using the gtk type-check macros, then there is no
need to first check that it isn't NULL).
+ (get_file_content): Signatures are now supposed to be in UTF-8 and
+ not the user's locale charset, so we must first read in the
+ content, then check that it is valid UTF-8. If it isn't, then we
+ need to try to convert it to UTF-8.
2002-07-22 Radek Doulik <rodo@ximian.com>