Re: strategy for dealing with new gettext po/ChangeLog editing
- From: James Henstridge <james daa com au>
- To: Owen Taylor <otaylor redhat com>
- Cc: <gtk-devel-list gnome org>, Darin Adler <darin bentspoon com>
- Subject: Re: strategy for dealing with new gettext po/ChangeLog editing
- Date: Mon, 11 Jun 2001 14:50:04 +0800 (WST)
On 9 Jun 2001, Owen Taylor wrote:
> For GLib and GTK+ we are simply avoiding gettextize entirely. The
> intl/ directory is useless for us, so, we:
>
> - Use glib-gettext.m4 which doesn't build libintl
> - Use a custom version of po/Makefile.in.in which doesn't need
> anything in the intl/ directory.
>
> I tend to think this is the approach we should be taking everywhere -
> you can't use the intl/ directory for a library, and I don't
> think it makes sense to have gnome-libs compiled without internationalization,
> but then have nautilus (or whatever) linking to a static version
> of libintl/.
>
> That does require checking in po/Makefile.in.in and po/po2tbl.sed
> but nothing else.
The current releases of gettext can build a shared library version of
libintl, so using gettext in libraries on systems without gettext in libc
is less of a problem than it was with 0.10.35. The issue of having a
GPL'd libintl as a dependency for libgtk might be a problem (although that
could be worked around by using the LGPL'd libintl sources in glibc).
James.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]