[PATCH 00/22] Mark more strings for translation

I originally wanted to have a look regularly at what's in 'pu', catch translatable strings that are not marked so and ask for updates. But I failed horribly at that, so for this cycle I just looked at all the changes between the last release and master and marked strings. This series probably

Re: [PATCH 00/22] Mark more strings for translation

On Sun, Feb 28, 2016 at 12:34 AM, Junio C Hamano wrote: > We'd still want the fixes to apply on top of relevant topics if we > could, as the fix to the topic itself (with or without i18n fixes), > when we discover that it has a huge flaw not desirable in v2.8.0, > might be to

Re: [PATCH 00/22] Mark more strings for translation

Junio C Hamano writes: > Thanks. "A new string we added since v2.7.0 that is not marked for > i18n" is a new i18n bug and "a string that used to be marked is not > marked when the code was rewritten since v2.7.0" is an i18n > regression, and we would want to "fix" both post

Re: [PATCH 00/22] Mark more strings for translation

Nguyễn Thái Ngọc Duy writes: > On Sat, Feb 27, 2016 at 6:41 AM, Junio C Hamano wrote: >> In previous cycles, I often left many topics in 'next' when tagging >> this zero-th preview, but eventually merged them before the final. >> I decided to do things a

[PATCH 00/22] Mark more strings for translation

On Sat, Feb 27, 2016 at 6:41 AM, Junio C Hamano wrote: > In previous cycles, I often left many topics in 'next' when tagging > this zero-th preview, but eventually merged them before the final. > I decided to do things a bit differently for this cycle: a topic, > once it hits