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: Sat, 12 Feb 2011 21:55:46 +0100 [thread overview]
Message-ID: <AANLkTinewf-TopnV9vzGrMqNMeBhH+O+0J68ueaoh8HB@mail.gmail.com> (raw)
In-Reply-To: <7vipwpxbam.fsf@alter.siamese.dyndns.org>
On Sat, Feb 12, 2011 at 21:12, Junio C Hamano <gitster@pobox.com> wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> Hi both. I've been on a hiatus from Git development, so I haven't
>> picked up ab/i18n again, but I still plan to and to get it included in
>> Git.
>
> Thanks.
>
>> *** TODO Introduce a skeleton no-op gettext, just the
>> infrastructure minus the interesting stuff
>>
>> I.e. just add:
>>
>> #define N_(s) (s)
>> #define _(s) (s)
>>
>> *** TODO Add no-op C gettextize patches
>>
>> This will change "foo" to _("foo") everywhere, but will be a no-op
>> due to it being macroed out.
>
> It would be best to get this as early as possible while not many topics
> are in 'next'; it is preferrable if we can rebase other topics in 'pu' on
> top of the result of this step.
>
>> *** TODO Add no-op Shell/Perl gettextize patches
>>
>> Due to the nature of these languages these can't be macroed out,
>> but it's still easy to have a no-op wrapper function.
>
> Yes. After the above two steps are done, we can pretty much independently
> advance and tweak i18n topic from other changes.
>
>> *** TODO Add po/README etc.
>>
>> The documentation about how to add translations etc.
>>
>> *** TODO Add translations
>>
>> Add the po/*.po files. Since we have no-op translations everywhere
>> we can translate git with xgettext + po editing, even though the
>> translations aren't being used yet.
>>
>> *** TODO Introduce the real gettext in a later patch + tests
>>
>> Once the rest is all in this will be a much smaller change.
>
> The last two could probably be swapped, but I think we are on the same
> page as to the overall steps and direction.
Right, good to hear we're on the same page.
I'll be doing a Perl release on the 20th, and I'm traveling around,
but I hope to get around to this sooner rather than later.
next prev parent reply other threads:[~2011-02-12 20:56 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 [this message]
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
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=AANLkTinewf-TopnV9vzGrMqNMeBhH+O+0J68ueaoh8HB@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).