2008/5/7 Jean-Yves Lefort <[EMAIL PROTECTED]>: > On Wed, 07 May 2008 01:02:02 +0100 > Bastien Nocera <[EMAIL PROTECTED]> wrote: > > > > > On Tue, 2008-05-06 at 16:54 -0700, Brian J. Tarricone wrote: > > > Bastien Nocera wrote: > > > > On Tue, 2008-05-06 at 19:41 -0400, Havoc Pennington wrote: > > > >> Hi, > > > >> > > > >> On Tue, May 6, 2008 at 4:15 PM, Felipe Contreras > > > >> <[EMAIL PROTECTED]> wrote: > > > >>> Is there any reason? > > > >>> > > > >> I don't know. If I had to guess, it probably wasn't seen as worth > > > >> maintaining. After all none of the other features of GLib have random > > > >> --disable-feature options. Searching in bugzilla might find related > > > >> bug discussion. > > > > > > > > And also because glib provides i18n for applications and libraries > above > > > > it, and convenience functions for UTF-8, etc. that wouldn't be > available > > > > on Unix systems without NLS support. > > > > > > Disabling NLS support might be quite useful for people on embedded > > > systems and/or people who are using glib for only a part of their > > > application and use a different translation framework. > > > > And it means that a lot of convenience functions for UTF-8 handling > > wouldn't work. > > Just FYI, that's not true. The GLib Unicode code does not require > gettext. Unicode support and message translation support are two > entirely different matters.
Exactly. AFAIK the only effect is that the messages from GLib won't be translated. For clients using the library there's no difference at all. -- Felipe Contreras _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list