Jean-Noël AVILA <[email protected]> writes:
> On Monday, 9 October 2017, 09:47:26 CEST Stefan Beller wrote:
>
>> I always assumed that translators are aware of these issues and sort of
>> work around this somehow, maybe like this:
>>
>> "submodule entry '%s' (%s) is not a commit. It is of type %s"
>
> Translators can be aware of the issue if the coder commented the
> internationalization string with some possible candidates for the
> placeholders
> when it is not clear unless you check in the source code. Much effort was
> poured into translating the technical terms in other parts of Git; it seems
> awkward to just step back in this occurence.
I do not see this particular case as "stepping back", though.
Our users do not spell "git cat-file -t commit v2.0^{commit}" with
'commit' translated to their language, right? Shouldn't an error
message output use the same phrase the input side requests users to
use?
