From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: i18n, gettext support
Date: Fri, 03 Sep 2004 11:34:01 +1000 [thread overview]
Message-ID: <87d614b0fq.fsf@zip.com.au> (raw)
In-Reply-To: <200409021821.13800.bruno@clisp.org> (Bruno Haible's message of "Thu, 2 Sep 2004 18:21:13 +0200")
Bruno Haible <bruno@clisp.org> writes:
>
> + SCM_API SCM scm_get_textdomain (void);
> + SCM_API SCM scm_set_textdomain (SCM domainname);
I think these could be a single textdomain func taking an optional
argument. That's what's done for setlocale for instance, and it
matches the C routines.
> + SCM_API SCM scm_get_textdomain_dir (SCM domainname);
> + SCM_API SCM scm_set_textdomain_dir (SCM domainname, SCM directory);
> + SCM_API SCM scm_get_textdomain_codeset (SCM domainname);
> + SCM_API SCM scm_set_textdomain_codeset (SCM domainname, SCM encoding);
And I'd call these bindtextdomain, again for similarity to the C
routines they wrap.
> + static int
> + scm_validate_category (SCM category, const char *subr, int pos)
> + {
> + if (scm_is_eq (category, scm_sym_LC_MESSAGES))
> + return LC_MESSAGES;
LC_MESSAGES and friends already exist as variables.
> + SCM_VARIABLE_SET (gettersym,
> + scm_make_procedure_with_setter (
> + SCM_VARIABLE_REF (gettersym),
> + SCM_VARIABLE_REF (settersym)));
Procedures with setters are not much used in the core.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-09-03 1:34 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 [this message]
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
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=87d614b0fq.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).