unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
Cc: guile-devel@gnu.org
Subject: Re: AM_GNU_GETTEXT weirdness
Date: Tue, 28 Sep 2004 18:07:21 +0200	[thread overview]
Message-ID: <200409281807.21775.bruno@clisp.org> (raw)
In-Reply-To: <874qln8cix.fsf@zagadka.ping.de>

Marius Vollmer wrote:
> >> running ./autogen.sh now runs gettextize

autoreconf shouldn't run gettextize. This was fixed in autoconf-2.57.

> >> and that causes some
> >> 'useless' things to happen, like the creation of po/

If you don't want a po/ directory, just don't run gettextize, and instead
do the steps (explained in the GNU gettext manual, chapter
"The Maintainer's View") manually.

> >> and the inclusion
> >> of po/Makefile.in in _all_ AC_CONFIG_FILES statements in configure.in.

This is a bug in gettextize that is fixed in the current gettext CVS
(not yet released; sorry).

> >>   Makefile.am:26: AM_GNU_GETTEXT used but `po' not in SUBDIRS

This is fixed in automake 1.8 and newer.

Jan Nieuwenhuizen wrote:

> > I have no clues whatsoever about what the developers of auto* have in
> > mind.  You'll have to ask Bruno about the AM_GNU_GETTEXT/libintl stuff.
> > What I had initially, was
> >
> >     dnl i18n tests
> >     AC_CHECK_HEADERS([libintl.h])
> >     AC_CHECK_FUNCS(gettext)
> >     if test $ac_cv_func_gettext = no; then
> >        AC_CHECK_LIB(intl, gettext)
> >     fi
> >     AC_CHECK_FUNCS([bindtextdomain textdomain])
> >
> > maybe something like that is better?
>
> Bruno, what is your view?

That autoconf test fails to detect an existing GNU libintl on _all_ platforms.
(Moreover it would pretend to have found gettext on Solaris without
GNU libintl, which would lead to linker errors later.)
Thus it works only on glibc systems, where no libintl is needed.

That's why I recommend the AM_GNU_GETTEXT macro.

> I have a hard time convincing myself now that gettext support should
> be in the core, when I have, for example, not accepted SCTP.  Hmm.

You have to estimate the importance of internationalization.

For illustration: In a new Linux magazine special issue about PHP 5, there
were about 6 or 7 introductory articles about this language and environment.
One of them was about how to use gettext from within PHP.

Bruno



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2004-09-28 16:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24  2:40 AM_GNU_GETTEXT weirdness Marius Vollmer
2004-09-24  7:17 ` Jan Nieuwenhuizen
2004-09-24 23:36   ` Marius Vollmer
2004-09-25  7:13     ` Jan Nieuwenhuizen
2004-09-28 16:07     ` Bruno Haible [this message]
2004-09-28 19:03       ` Marius Vollmer
2004-09-28 19:55         ` Bruno Haible
2004-09-28 21:13           ` Marius Vollmer
2004-09-25 21:30 ` Kevin Ryde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200409281807.21775.bruno@clisp.org \
    --to=bruno@clisp.org \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).