Re: What's cooking in git.git (Feb 2011, #06; Sun, 27)

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Mar 10, 2011, 09:44 UTC
Message-ID: <AANLkTikD2M=33B9E2mpBEmT5rLsZHPFc-T5Yqp3EMRJx@mail.gmail.com>
In-Reply-To: <m3k4gh7r0m.fsf@localhost.localdomain>

On Wed, Mar 2, 2011 at 11:32, Jakub Narebski <jnareb@gmail.com> wrote:

Show 8 quoted lines

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