From: Bagas Sanjaya <bagasdotme@gmail.com>
Date: Fri, 17 Sep 2021 07:41:56 GMT
Subject: Re: [PATCH 2/2] request-pull: mark translatable strings
Message-ID: <187b4b89-e037-6103-08f4-870ce8f1e4fd@gmail.com>
In-Reply-To: <xmqqbl4stg91.fsf@gitster.g>

On 17/09/21 03.30, Junio C Hamano wrote:
> So a good middle ground may be
> 
>   - allow translation, like these patches attempt
> 
>   - introduce the command line option "--l10n=<value>" and
>     the requestpull.l10n configuration variable that gives the
>     default for the option:
> 
>     - when it is set to 'true', end-user's local taken from the
>       environment is used as the target for translation.
> 
>     - when it is set to 'false', translation is turned off.
> 
>     - when it is set to any other value, the locale is set to the
>       value of that variable (imagine a Japanese developer
>       contributing to a German project).
> 
> perhaps?   I dunno.
> 

I'm leaning towards second option.

However, I proposed that --l10n and corresponding config 
requestpull.l10n just take locale value set, and defaults to English 
(en_US or C) if empty.

-- 
An old man doll... just what I always wanted! - Clara