From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: git@vger.kernel.org, Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Johannes Sixt" <j6t@kdbg.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"René Scharfe" <l.s.r@web.de>,
"Bagas Sanjaya" <bagasdotme@gmail.com>
Subject: Re: [PATCH 2/2] advice: refactor "action is not possible because you have unmerged files"
Date: Wed, 19 Jan 2022 16:42:35 +0100 [thread overview]
Message-ID: <3083234.G16DuhSZxH@cayenne> (raw)
In-Reply-To: <20220119094445.15542-3-bagasdotme@gmail.com>
On Wednesday, 19 January 2022 10:44:45 CET Bagas Sanjaya wrote:
> Factor action names (cherry-picking, committing, merging, pulling, and
> reverting) out of the message string.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> advice.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/advice.c b/advice.c
> index 1dfc91d176..4c72856478 100644
> --- a/advice.c
> +++ b/advice.c
> @@ -175,15 +175,15 @@ void list_config_advices(struct string_list *list,
const char *prefix)
> int error_resolve_conflict(const char *me)
> {
> if (!strcmp(me, "cherry-pick"))
> - error(_("Cherry-picking is not possible because you
have unmerged files."));
> + error(_("%s is not possible because you have unmerged
files."), "Cherry-picking");
> else if (!strcmp(me, "commit"))
> - error(_("Committing is not possible because you have
unmerged files."));
> + error(_("%s is not possible because you have unmerged
files."), "Commiting");
> else if (!strcmp(me, "merge"))
> - error(_("Merging is not possible because you have
unmerged files."));
> + error(_("%s is not possible because you have unmerged
files."), "Merging");
> else if (!strcmp(me, "pull"))
> - error(_("Pulling is not possible because you have
unmerged files."));
> + error(_("%s is not possible because you have unmerged
files."), "Pulling");
> else if (!strcmp(me, "revert"))
> - error(_("Reverting is not possible because you have
unmerged files."));
> + error(_("%s is not possible because you have unmerged
files."), "Reverting");
> else
> error(_("It is not possible to %s because you have
unmerged files."),
> me);
>
These strings don't qualify for factorization, because the words that you are
extracting are English words that need to be translated. We can only extract
words that are know to be constant, such as options, configuration, environment
variables.
Playing grammar lego with sentences makes it impossible for translators to find
a good translation.
JN
next prev parent reply other threads:[~2022-01-19 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 9:44 [PATCH 0/2] More similar messages refactoring Bagas Sanjaya
2022-01-19 9:44 ` [PATCH 1/2] sequencer: factor GIT_AUTHOR_* from message strings Bagas Sanjaya
2022-02-11 20:26 ` Jean-Noël AVILA
2022-01-19 9:44 ` [PATCH 2/2] advice: refactor "action is not possible because you have unmerged files" Bagas Sanjaya
2022-01-19 11:11 ` René Scharfe
2022-01-19 15:31 ` Ævar Arnfjörð Bjarmason
2022-01-19 15:42 ` Jean-Noël AVILA [this message]
2022-01-19 18:18 ` Junio C Hamano
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=3083234.G16DuhSZxH@cayenne \
--to=jn.avila@free.fr \
--cc=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=l.s.r@web.de \
/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).