Re: [L10N] Kickoff of translation for Git 2.14.0 round 1
- From
Jean-Noël Avila <jn.avila@free.fr>
- Date
- Jul 23, 2017, 02:43 UTC
- Message-ID
- <70aeede1-6052-94fb-71a5-ff2f5717098a@free.fr>
- In-Reply-To
- <1500742926.2744.4.camel@gmail.com>
Le 22/07/2017 à 19:02, Kaartic Sivaraam a écrit :
Show 7 quoted lines
> On Sat, 2017-07-15 at 21:30 +0200, Jean-Noël Avila wrote:
>> * commit 4ddb1354e8 ("status: contextually notify user about an initial
>> commit") plays sentence lego while introducing colorization which again
>> does not play well with i18n.
>>
> What, if anything, should be done about this?
>I only spotted it because the string is new for translation. But the previous version was already playing sentence lego. So this is not a regression ;-)
If I understand correctly, getting a i18n friendly string would require being able to "color_sprintf" the branche name, and then "color_fprintf" the output with a %s formatting string. None of this is already available and that would introduce cumbersome logic in the code.
More generally, i18n puts some pressure on coding style for sure, and it gets worse with multi-platform and coloring... how can we ease the burden of developpers on this front without resorting to ad hoc patches?