From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Harald Nordgren via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Harald Nordgren <haraldnordgren@gmail.com>
Subject: Re: [PATCH] remote: use plural-only message for diverged branch status
Date: Mon, 16 Mar 2026 10:49:26 +0000 [thread overview]
Message-ID: <75c85249-1cff-425a-8e77-98d55215c324@gmail.com> (raw)
In-Reply-To: <xmqqjyvdvo7t.fsf@gitster.g>
On 15/03/2026 02:08, Junio C Hamano wrote:
> Phillip Wood <phillip.wood123@gmail.com> writes:
>
>> There can be more than one form of the plural string though. The gettext
>> manual has the following example of the Polish translation of "file" for
>> different numbers of files [1]
>>
>> 1 plik
>> 2,3,4 pliki
>> 5-21 plików
>> 22-24 pliki
>> 25-31 plików
>>
>> ngettext() handles that correctly, translating a single string without
>> an associated count will not.
>
> That is a very interesting example, and a valid reason to have me
> retract the #leftoverbits that led to the patch being discussed.
>
> But wouldn't that lead to an awkward conclusion, i.e., hits from
> "git grep '[^Q]_("[^"]*%[id]' \*.c" are potential bugs that need to
> be updated to use ngettext().
I think it does - maybe we should suggest fixing these as a miroproject
for GSoC and Outreachy? It certainly looks like there are plenty of them.
Thanks
Phillip
> Of course, we need to exclude messages like "the error code %d was
> returned" and "you have a bug on line %d", but there seem to be real
> errors in randomly selected hits from the "git grep" output, e.g.,
>
> add-patch.c: _("Split into %d hunks."),
> archive-zip.c: return error(_("path too long (%d chars, SHA1: %s): %s"),
> builtin/checkout.c: die(_("'%s' matched multiple (%d) remote tracking branches"),
> builtin/credential-store.c: die_errno(_("unable to get credential storage lock in %d ms"), timeout_ms);
> builtin/describe.c: _("found %i tags; gave up search at %s\n"),
> builtin/fsck.c: fprintf_ln(stderr, _("Checking connectivity (%d objects)"), max);
>
> You can notice that I started from 'a' and stopped very early in 'b'
> ;-).
>
> Thanks.
next prev parent reply other threads:[~2026-03-16 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 9:12 [PATCH] remote: use plural-only message for diverged branch status Harald Nordgren via GitGitGadget
2026-03-14 9:16 ` [PATCH] checkout: add --autostash option for branch switching Harald Nordgren
2026-03-14 16:52 ` [PATCH] remote: use plural-only message for diverged branch status Junio C Hamano
2026-03-14 18:38 ` Junio C Hamano
2026-03-14 20:08 ` Phillip Wood
2026-03-15 2:08 ` Junio C Hamano
2026-03-16 10:49 ` Phillip Wood [this message]
2026-03-16 17:06 ` Junio C Hamano
2026-03-25 4:29 ` Kaartic Sivaraam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=75c85249-1cff-425a-8e77-98d55215c324@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=haraldnordgren@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox