unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
Cc: guile-devel@gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: AM_GNU_GETTEXT weirdness
Date: Tue, 28 Sep 2004 21:55:20 +0200	[thread overview]
Message-ID: <200409282155.20886.bruno@clisp.org> (raw)
In-Reply-To: <ljlleu9pxd.fsf@troy.dt.e-technik.uni-dortmund.de>

Marius Vollmer wrote:
> There is at least one gettext implementation in Scheme and maybe we
> could just ship that...

There's nothing wrong with emulating the C-written libintl library in a
higher-level language, in principle. Python, GNU Smalltalk, and OCaml,
for example, do this. They wrote all the necessary infrastructure
(character set converters - iconv() equivalent, and the code for parsing
and managing .mo files in memory) from scratch in their high-level language.
It's a choice of "slim vs. thick".

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".

Bruno



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2004-09-28 19:55 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 [this message]
2004-09-28 21:13           ` Marius Vollmer
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=200409282155.20886.bruno@clisp.org \
    --to=bruno@clisp.org \
    --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).