git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Robert Buck <buck.robert.j@gmail.com>
Cc: Jeff Epler <jepler@unpythonic.net>,
	Git Mailing List <git@vger.kernel.org>,
	Jakub Narebski <jnareb@gmail.com>,
	Dmitry Potapov <dpotapov@gmail.com>, Jan Hudec <bulb@ucw.cz>,
	Thomas Rast <trast@student.ethz.ch>,
	Marc Weber <marco-oweber@gmx.de>
Subject: Re: [PATCH] WIP: begin to translate git with gettext
Date: Tue, 18 May 2010 04:23:28 +0000	[thread overview]
Message-ID: <AANLkTikUGV8HnkJcz1LOmbpttAmyhf-IynRDZkyNwG6N@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikkfD_mfBz3mEpu_lP5heB-22QtI6FZP2eZ_C1g@mail.gmail.com>

On Mon, May 17, 2010 at 23:29, Robert Buck <buck.robert.j@gmail.com> wrote:
> Is gettext portable? Or is it only POSIX? If it's not portable, have
> you considered using ICU instead as it is the best of class solution
> for I18N/L10N?

Yes it's portable. libintl or libraries that provide compatible
interfaces are available on every platform Git is.

ICU is not a gettext replacement, it's a Unicode processing library, I
don't think it has any gettext-like features. In any case it would be
a huge dependency for the service it would provide.

  reply	other threads:[~2010-05-18  4:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 16:05 [PATCH] WIP: begin to translate git with gettext Jeff Epler
2010-05-17 23:29 ` Robert Buck
2010-05-18  4:23   ` Ævar Arnfjörð Bjarmason [this message]
2010-05-18  7:40 ` Michael J Gruber
2010-05-18  8:11   ` Ævar Arnfjörð Bjarmason
2010-05-18 16:40   ` Jeff Epler
2010-05-18 17:02     ` Ævar Arnfjörð Bjarmason
2010-05-20 16:02       ` Ævar Arnfjörð Bjarmason
2010-05-21 18:02         ` Dévai Tamás
     [not found] <20100517160208.GA20842@unpythonic.net>
2010-05-18 10:57 ` Ævar Arnfjörð Bjarmason
2010-05-18 16:07   ` Jeff Epler
2010-05-18 16:47     ` Ævar Arnfjörð Bjarmason

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=AANLkTikUGV8HnkJcz1LOmbpttAmyhf-IynRDZkyNwG6N@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=buck.robert.j@gmail.com \
    --cc=bulb@ucw.cz \
    --cc=dpotapov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jepler@unpythonic.net \
    --cc=jnareb@gmail.com \
    --cc=marco-oweber@gmx.de \
    --cc=trast@student.ethz.ch \
    /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).