It's pretty trivial to effectively disable NLS without GLib knowing by writing a minimal dummy libintl.c (and corresponding libintl.h) and compile it into a "fake" libintl.a, and then point the GLib configury at those with CPPFLAGS and LDFLAGS.
I did something similar mainly for Windows, but somebody told me it is useful on MacOSX, too: a "proxy" libintl that dynamically tries to load and use the real libintl, and falls back to nop semantics if it isn't found. The point with this is that end-user application packagers can then decide whether to include the real libintl binaries in their package or not, but still use the same GLib binaries in both cases. After all, if an app isn't localised, it doesn't make much sense if (just) messages from GLib (or GTK+) are localised. See http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/proxy-libintl-20080418.zip . --tml _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list