Re: [PATCH 04/11] sha1dc: mark forgotten message for translation
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jan 18, 2021, 14:26 UTC
- Message-ID
- <nycvar.QRO.7.76.6.2101181525370.52@tvgsbejvaqbjf.bet>
- In-Reply-To
- <YAHC9faa4ykNOWj6@coredump.intra.peff.net>
Hi Peff,
On Fri, 15 Jan 2021, Jeff King wrote:
Show 22 quoted lines
> On Fri, Jan 15, 2021 at 04:43:05PM +0100, Johannes Schindelin wrote:
>
> > > > - die("SHA-1 appears to be part of a collision attack: %s",
> > > > + die(_("SHA-1 appears to be part of a collision attack: %s"),
> > > > hash_to_hex_algop(hash, &hash_algos[GIT_HASH_SHA1]));
> > >
> > > I didn't find any list discussion, but I think I may have actually left
> > > this untranslated intentionally. Like a BUG(), we'd expect it to come up
> > > basically never. And when it does, being able to search for the exact
> > > wording online may be more important than providing a translated
> > > version.
> >
> > I disagree with that reasoning. By that rationale, any message we deem to
> > be somewhat rare should be _untranslated_.
> >
> > A much better rule, at least from my perspective is: is the target
> > audience the Git users? If so, the message is to be translated. If not,
> > then not.
>
> That's what I was getting at. The audience is really Git developers,
> just like it would be for a BUG(). We don't expect either of those
> things to happen.While a SHA-1 collision might not be anything we expect to happen, I am fairly certain it won't be a bug in Git causing it. Nor will it be anything that core Git developers have to react on. For those reasons, I disagree that core Git developers are the target audience of this message.
Ciao, Dscho