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 23:13:41 +0200 [thread overview]
Message-ID: <ljhdpi9jwa.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <200409282155.20886.bruno@clisp.org> (Bruno Haible's message of "Tue, 28 Sep 2004 21:55:20 +0200")
Bruno Haible <bruno@clisp.org> writes:
> Marius Vollmer wrote:
>> There is at least one gettext implementation in Scheme and maybe we
>> could just ship that...
>
> [...]
> When libintl added extra features for Farsi and Arabic, you get them for
> free by using libintl. With the emulation approach, you need to emulate
> this as well, or you cannot use .mo files that make use of these features.
> It's a choice of "reuse vs. reimplement".
Yes. I don't know much about i18n in general or gettext in
particular, and thus I have no real opinion on how complicated i18n is
and how much of that is covered by gettext. In general, I'm a huge
fan of factoring out stuff: we had our own bignum arithmetic, but now
we use GNU mp for it.
Not using gettext only because we can't get it integrated into the
configure cruft of Guile seems silly, in any case.
_______________________________________________
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 21:13 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
2004-09-28 19:55 ` Bruno Haible
2004-09-28 21:13 ` Marius Vollmer [this message]
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=ljhdpi9jwa.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).