Re: [PATCH] WIP: begin to translate git with gettext

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: May 20, 2010, 16:02 UTC
Message-ID: <AANLkTinksuRQ-XJrusR9PXeP0HowaK-6ZJh8uwxMFUg2@mail.gmail.com>
In-Reply-To: <AANLkTikbl3jDXzdBhd0w6jSXTD-q5kai6Sy6CKLVmRdD@mail.gmail.com>

On Tue, May 18, 2010 at 17:02, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:

Show 16 quoted lines

> On Tue, May 18, 2010 at 16:40, Jeff Epler <jepler@unpythonic.net> wrote:
>> The amount of work to mark all the source files and then to keep the
>> marks up to date should not be underestimated--and that's just the work
>> to enable translators to localize the software.  It is important to
>> gauge the interest in the git community in actually doing this work.
>
> It's also something you shouldn't overestimate. I've been involved in
> internationalizing several projects that were previously English-only.
>
> The work of making things translatable can be done incrementally. You
> also don't have to get everything right the first time, the current
> proof of concept translation of `git status` for instance suffers from
> numerous problems, but it's still better than nothing.
>
> It can be used as-is and then incrementally improved by arranging the
> strings more intelligently in the future.

I did some work on this in my branch: http://github.com/avar/git/compare/master...topic/git-gettext

Fixed up the Makefile rules a bit, added appropriate gitignores, and added a work in progress po/is.po.

Still have to go through the gettext manual to figure out how to integrate this with our shellscripts.