After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 83969 - Should libglade call bind_textdomain_codeset?
Should libglade call bind_textdomain_codeset?
Status: RESOLVED WONTFIX
Product: libglade
Classification: Deprecated
Component: general
0.x
Other Linux
: Normal normal
: ---
Assigned To: James Henstridge
James Henstridge
: 125715 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-06-03 12:57 UTC by Havoc Pennington
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Havoc Pennington 2002-06-03 12:57:25 UTC
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65866
Comment 1 James Henstridge 2002-06-03 14:13:30 UTC
It is the application's responsibility to set up its translation
domains.  Libglade simply makes use of the translation domains set up
by the application.  People don't expect gtk_init() to fool around
with their domains, I wouldn't have thought they would expect libglade
to either.

The gtk.glade.bindtextdomain() function is included in the python
bindings because there is no wrapper for it in the standard library
(the gettext module in python does not call into the C gettext lib).

In python 2.3, apparently there will be a locale.bindtextdomain()
function to do the work (I don't know if it will handle the codeset
part though -- might be worth checking).
Comment 2 James Henstridge 2003-10-29 02:58:53 UTC
*** Bug 125715 has been marked as a duplicate of this bug. ***
Comment 3 James Henstridge 2003-10-29 04:18:38 UTC
*** Bug 125715 has been marked as a duplicate of this bug. ***