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
