This is the mail archive of the
guile-gtk@sourceware.cygnus.com
mailing list for the Guile project.
Re: guile-gtk-0.17 i18n
- To: Hisao Suzuki <suzuki611 at okisoft dot co dot jp>
- Subject: Re: guile-gtk-0.17 i18n
- From: Marius Vollmer <mvo at zagadka dot ping dot de>
- Date: 22 Feb 2000 20:15:44 +0100
- Cc: guile-gtk at sourceware dot cygnus dot com
- References: <E12NAyJ-0000Pb-00@ares.sys1.ngo.okisoft.co.jp>
Hisao Suzuki <suzuki611@okisoft.co.jp> writes:
> Marius Vollmer <mvo@zagadka.ping.de> wrote:
>
> > Why do you have to call gtk_set_locale before gtk_init? Is there a
> > good reason for this or can it be considered a bug in Gtk+?
>
> gtk_init parses locale-specific gtkrc file(s) and opens a
> locale-specific input method via XOpenIM(3x) of Xlib. The
> locale is supposed to have been already set.
>
> [...]
>
> I don't know why gtk_init doesn't call gtk_set_locale. Maybe it
> is just a historical reason, or maybe some applications want to
> run in "C" locale against any LANG environment variable value.
Aha, I see. Basically, gtk_set_locale is a not a completely harmless
operation because it changes the environment of the whole process (via
setlocale) and not just for the Gtk+ library. This should maybe not
be done unconditionally.
However, I now think that gtk_set_locale is an important part of
initializing Gtk+ and I think it is reasonable to just expect all
programs to work correctly when setlocale has been called.
So, your change goes in!
[ I'm sorry, I know that this change has been requested previously,
and I turned it down then. ]
- Marius