git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Alban Gruin <alban.gruin@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] sequencer: mark messages for translation
Date: Mon, 30 Mar 2020 17:59:49 -0600	[thread overview]
Message-ID: <20200330235949.GC83990@syl.local> (raw)
In-Reply-To: <20200328130515.17550-1-alban.gruin@gmail.com>

Hi Alban,

This looks good to me. I scratched my head for a little while wondering
about why these weren't marked for translation originally. They were
added back during the initial conversion to C. Some of the strings had
English-ism's such as "1st", "2nd", and so on, but weren't.

Johannes notes in [1] that marking those strings for translation was a
topic to be left until after v2.10.1, but I think he is busy enough that
this was easy to drop in the shuffle :-).

So, I am glad that you're addressing this. If you wanted, it may be
worthwhile to distill some of this into the patch message. But the
changes themselves look good to me.

On Sat, Mar 28, 2020 at 02:05:15PM +0100, Alban Gruin wrote:
> Signed-off-by: Alban Gruin <alban.gruin@gmail.com>
> ---
>  sequencer.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/sequencer.c b/sequencer.c
> index 6fd2674632..ba13a9a63b 100644
> --- a/sequencer.c
> +++ b/sequencer.c
> @@ -3128,7 +3128,7 @@ static int do_exec(struct repository *r, const char *command_line)
>  	const char *child_argv[] = { NULL, NULL };
>  	int dirty, status;
>
> -	fprintf(stderr, "Executing: %s\n", command_line);
> +	fprintf(stderr, _("Executing: %s\n"), command_line);
>  	child_argv[0] = command_line;
>  	argv_array_pushf(&child_env, "GIT_DIR=%s", absolute_path(get_git_dir()));
>  	argv_array_pushf(&child_env, "GIT_WORK_TREE=%s",
> @@ -3841,7 +3841,7 @@ static int pick_commits(struct repository *r,
>  					fclose(f);
>  				}
>  				if (!opts->quiet)
> -					fprintf(stderr, "Rebasing (%d/%d)%s",
> +					fprintf(stderr, _("Rebasing (%d/%d)%s"),
>  						todo_list->done_nr,
>  						todo_list->total_nr,
>  						opts->verbose ? "\n" : "\r");
> @@ -4093,7 +4093,7 @@ static int pick_commits(struct repository *r,
>  			if (!opts->verbose)
>  				term_clear_line();
>  			fprintf(stderr,
> -				"Successfully rebased and updated %s.\n",
> +				_("Successfully rebased and updated %s.\n"),

>  				head_ref.buf);
>  		}
>
> --
> 2.25.0

Either way, if you decide to add more context to the commit message I'd
be glad, but this is probably just fine as-is, so please have my:

  Reviewed-by: Taylor Blau <me@ttaylorr.com>

Thanks,
Taylor

[1]: https://lore.kernel.org/git/alpine.DEB.2.20.1609011658300.129229@virtualbox/

      reply	other threads:[~2020-03-30 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 13:05 [PATCH] sequencer: mark messages for translation Alban Gruin
2020-03-30 23:59 ` Taylor Blau [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

  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=20200330235949.GC83990@syl.local \
    --to=me@ttaylorr.com \
    --cc=alban.gruin@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).