From: Kevin Ryde <user42@zip.com.au>
Cc: Bruno Haible <bruno@clisp.org>, guile-devel@gnu.org
Subject: Re: i18n, gettext support
Date: Thu, 02 Sep 2004 07:44:16 +1000 [thread overview]
Message-ID: <87isaxmzpr.fsf@zip.com.au> (raw)
In-Reply-To: <87zn4ayn13.fsf@peder.flower> (Jan Nieuwenhuizen's message of "Wed, 01 Sep 2004 18:25:12 +0200")
Jan Nieuwenhuizen <janneke@gnu.org> writes:
>
> +SCM_API SCM scm_gettext (SCM string);
dgettext is good too, and may as well have dcgettext at the same time.
> +SCM_API SCM scm_bindtextdomain (SCM domainname, SCM directory);
bind_textdomain_codeset will be good too until guile gets a strong
grip on coding matters. (I would use it for instance to force utf8
for strings for gtk.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-09-01 21:44 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
2004-09-01 21:44 ` Kevin Ryde [this message]
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=87isaxmzpr.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=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).