From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: kev <kev@riseup.net>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: How you can translate things now, and a plan for the i18n series going forward
Date: Sat, 12 Feb 2011 12:19:17 +0100 [thread overview]
Message-ID: <AANLkTim+_zRisVRfnv_Xe69xof3e8rL_BAXxmAsCwins@mail.gmail.com> (raw)
On Fri, Feb 11, 2011 at 21:22, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> On Fri, Feb 11, 2011 at 21:01, kev <kev@riseup.net> wrote:
>> i understand the ab/i18n has been gettextized and translated to at
>> least a couple of languages.
>>
>> ive found references in the list archives to this, but nothing in the
>> source code. i do see translations of git-gui, however. but im looking
>> for some clue as to how to translate git itself.
>
> Currently the ab/i18n branch has not been merged to master, so it's
> not available to the general public. Ævar has been working on it but
> we haven't heard from him recently on this topic.
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.
Meanwhile Kev, if you want to translate Git you can:
git clone git://github.com/avar/git.git &&
cd git &&
git checkout -t origin/ab/i18n
And follow the instructions in po/README. This branch is relatively
out of date and hasn't been rebased on the upstream master in a while,
but most of the strings you'll be translating will still be there once
I do that, so your work won't go to waste.
For everyone else, I plan to re-submit ab/i18n, but re-do it so that
it isn't all one huge patch series but can be applied in smaller
steps. Here's the outline of my current plan:
** TODO Re-do the i18n series so it can be applied in piecemeal steps
I.e. these:
*** 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.
*** 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.
*** 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.
I think doing it this way will be much easier for everyone, what do
you think Junio?
next reply other threads:[~2011-02-12 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 11:19 Ævar Arnfjörð Bjarmason [this message]
2011-02-12 12:12 ` How you can translate things now, and a plan for the i18n series going forward 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
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=AANLkTim+_zRisVRfnv_Xe69xof3e8rL_BAXxmAsCwins@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).