From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: i18n, gettext support
Date: Thu, 02 Sep 2004 19:32:52 +0200 [thread overview]
Message-ID: <87k6vca857.fsf@peder.flower> (raw)
In-Reply-To: <200409021806.43157.bruno@clisp.org> (Bruno Haible's message of "Thu, 2 Sep 2004 18:06:43 +0200")
Bruno Haible writes:
> The autoconf test is still broken: AC_CHECK_LIB(intl, gettext) doesn't work.
Hmm, that's strange, I just copied the socket/connect; probably should
have tested it.
> Also your patch uses SCM_STRING_CHARS, which is deprecated
We used that in LilyPond, but it's just been deprecated so it seems.
> Find here an extended patch.
Thanks, please apply.
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-09-02 17:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 20:26 i18n, gettext support Bruno Haible
2004-08-23 0:58 ` Kevin Ryde
2004-09-01 16:25 ` Jan Nieuwenhuizen
2004-09-01 20:57 ` Bruno Haible
2004-09-02 9:38 ` Jan Nieuwenhuizen
2004-09-02 16:06 ` Bruno Haible
2004-09-02 16:21 ` Bruno Haible
2004-09-03 1:34 ` Kevin Ryde
2004-09-04 17:25 ` Bruno Haible
2004-09-07 0:13 ` Kevin Ryde
2004-09-07 12:38 ` Bruno Haible
2004-09-08 1:10 ` Kevin Ryde
2004-09-07 8:20 ` Jan Nieuwenhuizen
2004-09-07 14:16 ` Jan Nieuwenhuizen
2004-09-08 1:15 ` Kevin Ryde
2004-09-08 8:58 ` Jan Nieuwenhuizen
2004-09-08 10:39 ` Bruno Haible
2004-09-08 14:37 ` Jan Nieuwenhuizen
2004-09-08 16:37 ` Bruno Haible
2004-09-08 21:53 ` Jan Nieuwenhuizen
2004-09-08 22:45 ` Kevin Ryde
2004-09-08 23:46 ` Jan Nieuwenhuizen
2004-09-09 16:25 ` Jan Nieuwenhuizen
2004-09-15 11:20 ` Bruno Haible
2004-09-22 0:42 ` Marius Vollmer
2004-09-22 14:55 ` Bruno Haible
2004-09-02 17:32 ` Jan Nieuwenhuizen [this message]
2004-09-01 21:44 ` 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=87k6vca857.fsf@peder.flower \
--to=janneke@gnu.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).