Re: format-patch: why are the Range-diff: and Interdiff: headers translated?
Show 22 quoted lines
> Le 23 sept. 2025 à 20:42, Jeff King <peff@peff.net> a écrit :
>
> On Tue, Sep 23, 2025 at 09:59:55PM +0200, Kristoffer Haugsbakk wrote:
>
>> I’m not concerned about machine-readability. My thought was that
>> localization/l10n of this software was intended for the user themselves.
>> And also that users might, without intending to do so necessarily, end
>> up using localized output in contexts where they do want English
>> strings, like on an English-language mailing list. Even though they
>> might prefer Spanish (from my Colombian example) when using Git
>> themselves.
>>
>> But there might for all I know be Colombian/Latin American patch mailing
>> lists where localization like this works great.
>>
>> I’m not really in the natural target group for l10n Git. I might be
>> totally missing all the use-cases here.
>
> I'm not a user of the l10n stuff either, so you can take my opinion with
> a grain of salt. But it seems obvious to me that "the language I am most
> comfortable using" and "the language for the project I am contributing
> to" might not necessarily be the same.
Yep. My own patches have probably come in with French titles here because I set LANG that way.
Show 9 quoted lines
> I'm not sure how well gettext supports this use case, though. The first
> one should obviously come from LANG, etc. If we added a hypothetical
> format.lang config option, is there a way to tell gettext to translate a
> string using a language string provided per-call, rather than from the
> environment?
>
> I don't know that anybody is really even asking for this, so I'm not
> proposing to spend a lot of effort on it. But the thread made me wonder
> what is even possible/easy to do here.
I’m not asking at the moment, since it hasn’t bothered anyone. If it does and there’s a need to do something else, I’ll fix my workflow (opting in to such new config or otherwise, as the case may be).
Ben Knoble <ben.knoble@gmail.com>