From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: git@vger.kernel.org, "Jonathan Tan" <jonathantanmy@google.com>,
"Christopher Diaz Riveros" <christopher.diaz.riv@gmail.com>,
"Jean-Noël Avila" <jn.avila@free.fr>,
"Daniel Santos" <hello@brighterdan.com>
Subject: Re: [PATCH] fetch-pack: add TRANSLATORS notice for packfile ready messages
Date: Mon, 15 Nov 2021 16:21:41 +0100 [thread overview]
Message-ID: <211115.86ilwtsasb.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <2a4428a5-91d9-a0a5-39cd-eefa1c92024e@gmail.com>
On Mon, Nov 15 2021, Bagas Sanjaya wrote:
> On 14/11/21 16.50, Ævar Arnfjörð Bjarmason wrote:
>> If something isn't meant to be translated do this instead:
>> die(_("expected no other sections to be sent after no '%s"),
>> "ready");
>> I.e. pass it as a parameter.
>> There can then be a "TRANSLATORS" comment that explains that it's
>> the
>> string "ready", in reference to that protocol keyword. We do it that way
>> in various other places, and it completely avoids the potential problem
>> of a should not be translated string being translated.
>>
>
> Something like:
> /* TRANSLATORS: The 'ready' string is the protocol keyword. Leave it
> as is. */ ?
No, e.g. "TRANSLATORS: The parameter will be 'ready', a protocol
keyword" or something.
I.e. you don't need to instruct them to leave it as-is if there's no way
they can't leave it as-is, since it's being passed as a parameter.
> But I have admitted that I lean to your suggestion.
Yes you could also embed it in the string, but why do that in this case?
Seems like zero benefit, and potential translator confusion.
prev parent reply other threads:[~2021-11-15 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 7:31 [PATCH] fetch-pack: add TRANSLATORS notice for packfile ready messages Bagas Sanjaya
2021-11-14 9:50 ` Ævar Arnfjörð Bjarmason
2021-11-15 5:41 ` Bagas Sanjaya
2021-11-15 15:21 ` Ævar Arnfjörð Bjarmason [this message]
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=211115.86ilwtsasb.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=christopher.diaz.riv@gmail.com \
--cc=git@vger.kernel.org \
--cc=hello@brighterdan.com \
--cc=jn.avila@free.fr \
--cc=jonathantanmy@google.com \
/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;
as well as URLs for NNTP newsgroup(s).