Re: [PATCH v2 4/7] i18n: builtin/pull.c: mark strings for translation

From: Jean-Noël Avila <avila.jn@gmail.com>
Date: Apr 29, 2016, 06:57 UTC
Message-ID: <572305EE.8040704@gmail.com>
In-Reply-To: <CACsJy8BsxZTChST8Gb25LT1HwwR1AcAthjfOQmoAjxkF4qzvBw@mail.gmail.com>

Le 12/04/2016 11:52, Duy Nguyen a écrit :

Show 6 quoted lines

>
> Ex-translator speaking. Context is important. If it's me, I would even
> go as far as marking the whole line translatable just to give more
> context (it's mostly just copy and translate a few words then). But
> then again, I was half developer half translator and may see things a
> bit differently. Maybe _("<remote>") is a good balance.

I second this opinion. Translating a single word without context is generally not advised. The english word might come up in different situations with different grammatical forms for the translated version.

Adding the brackets provides enough context, as long as the string is always used in the same semantic field, describing the command line. I just don't know how much that helps reducing the amount of translated strings.

JN