From: Elijah Newren <newren@gmail.com>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] merge-ort: split "distinct types" message into two translatable messages
Date: Mon, 10 May 2021 12:29:45 -0700 [thread overview]
Message-ID: <CABPp-BFa484zCeXpzZ36ev2pBfDCH=Kp4wWWF_hZSQvgrf3LYA@mail.gmail.com> (raw)
In-Reply-To: <20210509215250.33215-1-alexhenrie24@gmail.com>
On Sun, May 9, 2021 at 2:53 PM Alex Henrie <alexhenrie24@gmail.com> wrote:
>
> The word "renamed" has two possible translations in many European
> languages depending on whether one thing was renamed or two things were
> renamed. Give translators freedom to alter any part of the message to
> make it sound right in their language.
>
> Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
> ---
> merge-ort.c | 21 +++++++++++++++------
> 1 file changed, 15 insertions(+), 6 deletions(-)
>
> diff --git a/merge-ort.c b/merge-ort.c
> index 6c2792b10e..745a844b18 100644
> --- a/merge-ort.c
> +++ b/merge-ort.c
> @@ -3050,12 +3050,21 @@ static void process_entry(struct merge_options *opt,
> rename_b = 1;
> }
>
> - path_msg(opt, path, 0,
> - _("CONFLICT (distinct types): %s had different "
> - "types on each side; renamed %s of them so "
> - "each can be recorded somewhere."),
> - path,
> - (rename_a && rename_b) ? _("both") : _("one"));
> + if (rename_a && rename_b) {
> + path_msg(opt, path, 0,
> + _("CONFLICT (distinct types): %s had "
> + "different types on each side; "
> + "renamed both of them so each can "
> + "be recorded somewhere."),
> + path);
> + } else {
> + path_msg(opt, path, 0,
> + _("CONFLICT (distinct types): %s had "
> + "different types on each side; "
> + "renamed one of them so each can be "
> + "recorded somewhere."),
> + path);
> + }
>
> ci->merged.clean = 0;
> memcpy(new_ci, ci, sizeof(*new_ci));
> --
> 2.31.1
I don't know much on the translation side (thanks for fixing it up for
me), but looks innocuous and correct from the code side:
Acked-by: Elijah Newren <newren@gmail.com>
next prev parent reply other threads:[~2021-05-10 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 21:52 [PATCH] merge-ort: split "distinct types" message into two translatable messages Alex Henrie
2021-05-10 5:36 ` Bagas Sanjaya
2021-05-10 5:50 ` Bagas Sanjaya
2021-05-10 16:42 ` Alex Henrie
2021-05-10 19:29 ` Elijah Newren [this message]
2021-05-10 22:33 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABPp-BFa484zCeXpzZ36ev2pBfDCH=Kp4wWWF_hZSQvgrf3LYA@mail.gmail.com' \
--to=newren@gmail.com \
--cc=alexhenrie24@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).