From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Sverre Rabbelier <srabbelier@gmail.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2011, #06; Sun, 27)
Date: Thu, 10 Mar 2011 10:44:31 +0100 [thread overview]
Message-ID: <AANLkTikD2M=33B9E2mpBEmT5rLsZHPFc-T5Yqp3EMRJx@mail.gmail.com> (raw)
In-Reply-To: <m3k4gh7r0m.fsf@localhost.localdomain>
On Wed, Mar 2, 2011 at 11:32, Jakub Narebski <jnareb@gmail.com> wrote:
> Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:
>> Don't know how it's handled in shell scripts or perl or whatever other
>> language (which does not use gettext?)
>
> Both shell scripts and Perl scripts would use gettext: gettext.sh for
> shell, Locale::Messages for Perl (we need lower level than Text::Domain,
> and Locale::Maketext is first no longer recommended, and second does
> not use gettext at least by default).
The i18n series uses Locale::Maketext:
https://github.com/avar/git/blob/ab%2Fi18n/perl/Git/I18N.pm
What do you mean it's not recommended? There are some articles about
Perl i18n saying you shouldn't use it, effectively because:
* Building GNU gettext is hard, let's go shopping.
* There were some bugs in it, which do not apply to us.
So using it is fine. I might still write some Gettext::XS::Tiny module
that works with both GNU gettext and Solaris, stick it on the CPAN and
make us depend on it. It would more closely align with what we
need. But that's something for the far future.
next prev parent reply other threads:[~2011-03-10 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 6:48 What's cooking in git.git (Feb 2011, #06; Sun, 27) Junio C Hamano
2011-02-28 13:22 ` Sverre Rabbelier
2011-02-28 16:52 ` Junio C Hamano
2011-03-01 20:54 ` Jeff King
2011-03-02 2:07 ` Junio C Hamano
2011-03-02 21:27 ` Jeff King
2011-03-02 5:24 ` Junio C Hamano
2011-03-02 7:17 ` Piotr Krukowiecki
2011-03-02 10:32 ` Jakub Narebski
2011-03-10 9:44 ` Ævar Arnfjörð Bjarmason [this message]
2011-03-10 16:37 ` Jakub Narebski
2011-03-02 21:28 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikD2M=33B9E2mpBEmT5rLsZHPFc-T5Yqp3EMRJx@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
--cc=piotr.krukowiecki@gmail.com \
--cc=srabbelier@gmail.com \
/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 NNTP newsgroup(s).