summaryrefslogtreecommitdiff
path: root/README.in
diff options
context:
space:
mode:
authorOwen Taylor <otaylor@redhat.com>2002-03-08 15:50:54 +0000
committerOwen Taylor <otaylor@src.gnome.org>2002-03-08 15:50:54 +0000
commitcef5d28c897af6b057d04420ebd040e70e5a693e (patch)
tree8f8cd049bb2b4923c82bb04941da7b832248e6d9 /README.in
parentdac25522cd299436ac1a7fe366e66d9a348e1715 (diff)
Final updates for 2.0.0
Fri Mar 8 10:20:46 2002 Owen Taylor <otaylor@redhat.com> * NEWS: Final updates for 2.0.0 * glib/gstrfuncs.c: Convert the results of strerror() and strsignal() to UTF-8. * glib/gconvert.c glib/gdir.c glib/giochannel.c glib/giounix.c glib/giowin32.c: Use g_strerror(), not strerror().
Diffstat (limited to 'README.in')
-rw-r--r--README.in4
1 files changed, 0 insertions, 4 deletions
diff --git a/README.in b/README.in
index e530b0d98..fe5f9cea2 100644
--- a/README.in
+++ b/README.in
@@ -34,10 +34,6 @@ Notes about GLib-2.0.0
Application programmers should not call g_locale_to_utf8() on these
strings.
-* The results of g_strerror() are currently in the encoding of the locale
- rather than in UTF-8. Again, this is a bug, and not behavior that
- should be relied upon.
-
* Similarly, the GLib error logging functions such as g_print(), g_warning(),
g_error(), currently do not convert the strings they are passed from
UTF-8 to the encoding of the locale, or check that the strings they