On Mon, 2008-06-16 at 15:18 -0500, Shaun McCance wrote:
> On Mon, 2008-06-16 at 20:48 +0100, Alan Cox wrote:
> > > Well, as I said, in this case:
> > >
> > > gtk_label_new(_(some_string));
> > >
> > > The output of gettext can (and often will) be UTF-8,
> > > so gtk_label_new is going to receive UTF-8 whether
> > > some_string is ASCII or not. If it's not UTF-8-safe,
> > > we're pretty much screwed already.
> >
> > No no no
> >
> > The output of _("blah") is "blah" for C locale, and "blah" should be
> > ASCII. You should only receive UTF-8 as the return from _("foo") in a
> > UTF-8 locale.
> >
> > It isn't about being "UTF-8 safe" it is about "expecting UTF-8 in this
> > locale".
>
> If gettext is returning anything but UTF-8, we have
> a lot of bugs in our application code. Because all
> of us just pass that stuff off to GTK+, and GTK+
> always expects UTF-8, regardless of the locale.
For how this is handled by glib and gtk+, see the man page for
bind_textdomain_codeset.
Not that there is any excuse to use something other than a UTF-8 local
these days.
- Owen
_______________________________________________
desktop-devel-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
