As James says on Simos's blog post, all strings inside GTK apps are
defined to be UTF-8 regardless of locale. GLib and GTK will convert on
the fly to locale encoding if they print to a terminal. So there
should be no issue with "C" locale other than possibly some odd
escaping. (Which could in theor
On Wed, 14 May 2008 04:17:09 -0400
"Havoc Pennington" <[EMAIL PROTECTED]> wrote:
> As James says on Simos's blog post, all strings inside GTK apps are
> defined to be UTF-8 regardless of locale. GLib and GTK will convert on
> the fly to locale encoding if they print to a terminal.
gtk may do, but
Hi.
I tried building everything with jhbuild today and noticed a few things
that need attention:
- glib trunk has changed the _() macro to take a const char * now and
some modules break because of this. Most notably nautilus, ekiga, dasher
and probably a few more. Other modules will have a bunch
El mar, 20-05-2008 a las 00:15 +0200, Kjartan Maraas escribió:
>
> I tried building everything with jhbuild today and noticed a few
> things that need attention:
Add to that gnome-python having problems to be detected by modules
depending on it due to waf 1.3.2 being used. I already fixed that by
