From 90d93042c2956f64838edb46ee43e8f02b7c7a24 Mon Sep 17 00:00:00 2001 From: Owen Taylor Date: Thu, 28 Mar 2002 23:24:23 +0000 Subject: Remove warning about g_print, etc, encoding. Thu Mar 28 18:22:53 2002 Owen Taylor * README: Remove warning about g_print, etc, encoding. * NEWS: Updates. * glib/gmessages.c (g_log_default_handler): Use %lu (plus a cast) when printing out pid_t arguments. (#76770, Morten Welinder) * glib/gstrfuncs.c (g_strdup_vprintf): Check the result of vasprintf(), return NULL on failure. (#76802, Akira Tagoh) * tests/testglib.c (TEST): Supress a warning with some GCC versions. --- README | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) (limited to 'README') diff --git a/README b/README index 5116c8930..ac8ba03cd 100644 --- a/README +++ b/README @@ -24,23 +24,16 @@ Installation See the file 'INSTALL' -Notes about GLib-2.0.0 +Notes about GLib-2.0.1 ====================== * On systems without the libintl from GNU gettext() or a recent version of the GNU C library, the encoding of translated error messages will be incorrect (they should be in UTF-8). A workaround for this is to install - GNU gettext and use that libintl. This is expected to be fixed in GLib-2.0.1. + GNU gettext and use that libintl. This is expected to be fixed in GLib-2.0.2. Application programmers should not call g_locale_to_utf8() on these strings. -* 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 - are passed are valid UTF-8. They should, despite this, be assumed to take - UTF-8 arguments. - - How to report bugs ================== -- cgit v1.2.3-70-g09d2