From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>, kev <kev@riseup.net>,
git@vger.kernel.org
Subject: Re: How you can translate things now, and a plan for the i18n series going forward
Date: Thu, 17 Feb 2011 09:47:07 +0100 [thread overview]
Message-ID: <AANLkTikij+hp7Q2Brfnp7ZiQgaZvhNcQBSijQozMtiH4@mail.gmail.com> (raw)
In-Reply-To: <7v8vxfh4j7.fsf@alter.siamese.dyndns.org>
On Thu, Feb 17, 2011 at 01:46, Junio C Hamano <gitster@pobox.com> wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> Here's a work-in-progress version of this:
>> https://github.com/avar/git/compare/master...ab/i18n-c-_-only
>>
>> I still have to:
>>
>> * Add NO_GETTEXT_POISON to more tests, some things have broken due to
>> new strings / changed tests.
>>
>> * Squash the !fixup patches in appropriately.
>>
>> But otherwise does this seem good? I.e. having just those stub macros,
>> a lot of *.c patches, including gettext.h in cache.h.
>
> I only gave a cursory look to "git diff master..ab/i18n-c-_-only" output,
> and things looked fine for a yet-to-be-completed WIP (I didn't see the
> definition of shell version of gettext and gettext_eval, for example).
I'm going to submit the C ones first, and do the shell and Perl ones
later if that's OK with you.
prev parent reply other threads:[~2011-02-17 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 11:19 How you can translate things now, and a plan for the i18n series going forward Ævar Arnfjörð Bjarmason
2011-02-12 12:12 ` Michael J Gruber
2011-02-12 20:12 ` Junio C Hamano
2011-02-12 20:55 ` Ævar Arnfjörð Bjarmason
2011-02-16 23:57 ` Ævar Arnfjörð Bjarmason
2011-02-17 0:46 ` Junio C Hamano
2011-02-17 8:47 ` Ævar Arnfjörð Bjarmason [this message]
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikij+hp7Q2Brfnp7ZiQgaZvhNcQBSijQozMtiH4@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kev@riseup.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).