From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: AM_GNU_GETTEXT weirdness
Date: Tue, 28 Sep 2004 21:03:26 +0200 [thread overview]
Message-ID: <ljlleu9pxd.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <200409281807.21775.bruno@clisp.org> (Bruno Haible's message of "Tue, 28 Sep 2004 18:07:21 +0200")
Bruno Haible <bruno@clisp.org> writes:
> Marius Vollmer wrote:
>> >> running ./autogen.sh now runs gettextize
>
> autoreconf shouldn't run gettextize. This was fixed in autoconf-2.57.
Ahh, OK. I think I have it sorted out now, and have reverted our
configure.in to use AM_GNU_GETTEXT. Hacking on guile-core from CVS
will now require GNU gettext, but that is OK.
> 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.
In other words, it is buggy, right?
>> 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.
Yep, and also the importance of using the platform's gettext for it.
There is at least one gettext implementation in Scheme and maybe we
could just ship that...
In any case, with up-to-date-enough tools, everything seems to work
fine right now. Thanks!
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-09-28 19:03 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
2004-09-28 19:03 ` Marius Vollmer [this message]
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=ljlleu9pxd.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--cc=guile-devel@gnu.org \
--cc=janneke@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).