Re: [PATCH/RFC v4 1/7] Add infrastructure for translating Git with gettext

From: Peter Krefting <peter@softwolves.pp.se>
Date: Jun 2, 2010, 11:31 UTC
Message-ID: <alpine.DEB.2.00.1006021224170.4751@ds9.cixit.se>
In-Reply-To: <AANLkTinzZUaFBzNHzxBA94ECeUKdejVGqSQF1TUtOrrk@mail.gmail.com>

Ævar Arnfjörð Bjarmason:

> But maybe that's counter-productive. Just making the English strings 
> translatable as-is is still going to make most of Git translatable, and it 
> isn't going to be that bad for languages like German and French.

I think this is the best approach. Without actually making *everything* available for translation it is impossible to weed out the problems. Some of the easier "hack" strings (plural word%s, sentence %s%s building, etc) can be fixed during conversion, the rest can be done later as complai^Wcomments come in.

> It would be useful to have an example of a message that could use 
> pluralization, even better examples in all of C, Perl and Shell.

There is the "Your branch is ahead of..." messages, they were introduced in commit b0030db331141bedfaf02f34a83f18712c0ae011, and are currently using a "commit%s" form, where the %s either maps to an empty string or "s". Should be fairly trivial to fix. I think there are other examples as well, but that's the first one I came to think of. :-)

-- 
\\// Peter - http://www.softwolves.pp.se/