summaryrefslogtreecommitdiff
path: root/glib/ggettext.c
diff options
context:
space:
mode:
Diffstat (limited to 'glib/ggettext.c')
-rw-r--r--glib/ggettext.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/glib/ggettext.c b/glib/ggettext.c
index 42f3d0e72..71654fb84 100644
--- a/glib/ggettext.c
+++ b/glib/ggettext.c
@@ -362,12 +362,12 @@ _g_dgettext_should_translate (void)
* translations for the current locale.
*
* The advantage of using this function over dgettext() proper is that
- * libraries using this function (like GTK+) will not use translations
+ * libraries using this function (like GTK) will not use translations
* if the application using the library does not have translations for
* the current locale. This results in a consistent English-only
* interface instead of one having partial translations. For this
* feature to work, the call to textdomain() and setlocale() should
- * precede any g_dgettext() invocations. For GTK+, it means calling
+ * precede any g_dgettext() invocations. For GTK, it means calling
* textdomain() before gtk_init or its variants.
*
* This function disables translations if and only if upon its first
@@ -385,7 +385,7 @@ _g_dgettext_should_translate (void)
*
* Note that this behavior may not be desired for example if an application
* has its untranslated messages in a language other than English. In those
- * cases the application should call textdomain() after initializing GTK+.
+ * cases the application should call textdomain() after initializing GTK.
*
* Applications should normally not use this function directly,
* but use the _() macro for translations.