From: Bruno Haible <bruno@clisp.org>
Subject: Re: doc gettext
Date: Mon, 10 Jan 2005 22:11:05 +0100 [thread overview]
Message-ID: <200501102211.05669.bruno@clisp.org> (raw)
In-Reply-To: <873bxarzgk.fsf@zip.com.au>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Kevin Ryde wrote:
> I'm looking at the text below to expand what's in the guile reference
> manual for gettext.
You can also use text from my original proposal (attached). It has the merit
of explaining the terms (domain, category, ...) that are used in the refman.
Also it contains complete workable examples. (You need to change the set!
notation to the optional-argument notation that is used in guile, though.)
> I'm a bit unsure about bind-textdomain-codeset. Thinking about it, if
> Guile gets its own notion of coding systems or whatever in the future
> then I'm wondering if that function might become obsolete, or even
> actively harmful.
When that happens, the bind-textdomain-codeset function should become a
nop.
> It does some good now, but maybe some strong
> warning against possible future change is needed.
But since in the present this function is _necessary_, I don't think it's
useful to make people doubt whether they should use it or not.
When bind-textdomain-codeset is no longer needed, you can easily make
the compiler emit a warning when it's used.
Bruno
[-- Attachment #2: guile-gettext.html --]
[-- Type: text/html, Size: 17344 bytes --]
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-01-10 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 22:48 doc gettext Kevin Ryde
2005-01-10 21:11 ` Bruno Haible [this message]
2005-01-23 23:20 ` Kevin Ryde
[not found] ` <200501202239.07346.bruno@clisp.org>
[not found] ` <87d5vzd6bb.fsf@zip.com.au>
2005-01-21 12:09 ` building guile from CVS Bruno Haible
2005-01-21 14:06 ` Marius Vollmer
2005-01-21 15:41 ` Bruno Haible
2005-01-21 21:45 ` Kevin Ryde
2005-01-22 14:03 ` Marius Vollmer
2005-01-24 15:25 ` Bruno Haible
2005-02-28 1:17 ` Marius Vollmer
2005-02-28 1:31 ` Marius Vollmer
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=200501102211.05669.bruno@clisp.org \
--to=bruno@clisp.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).