git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Vasco Almeida <vascomalmeida@sapo.pt>
Cc: Git <git@vger.kernel.org>
Subject: Re: [PATCH] i18n: notes: mark comment for translation
Date: Thu, 21 Jul 2016 12:45:22 +0200	[thread overview]
Message-ID: <CACBZZX51K=D2gYbzKvJW3B5=bzxEGGFhOc6TkAfJkkpdYuEt0w@mail.gmail.com> (raw)
In-Reply-To: <1469095670-3834-1-git-send-email-vascomalmeida@sapo.pt>

On Thu, Jul 21, 2016 at 12:07 PM, Vasco Almeida <vascomalmeida@sapo.pt> wrote:
> Mark comment displayed when editing a note for translation.

I'm not sure, but wouldn't this make more sense:

> Signed-off-by: Vasco Almeida <vascomalmeida@sapo.pt>
> ---
>  builtin/notes.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/builtin/notes.c b/builtin/notes.c
> index 0572051..37933bd 100644
> --- a/builtin/notes.c
> +++ b/builtin/notes.c
> @@ -91,7 +91,7 @@ static const char * const git_notes_get_ref_usage[] = {
>  };
>
>  static const char note_template[] =
> -       "\nWrite/edit the notes for the following object:\n";
> +       N_("\nWrite/edit the notes for the following object:\n");
+       N_("Write/edit the notes for the following object:");
>
>  struct note_data {
>         int given;
> @@ -179,7 +179,7 @@ static void prepare_note_data(const unsigned char *object, struct note_data *d,
>                         copy_obj_to_fd(fd, old_note);
>
>                 strbuf_addch(&buf, '\n');
+                 strbuf_addch(&buf, '\n');
> -               strbuf_add_commented_lines(&buf, note_template, strlen(note_template));
> +               strbuf_add_commented_lines(&buf, _(note_template), strlen(_(note_template)));
+                 strbuf_addch(&buf, '\n');
>                 strbuf_addch(&buf, '\n');
>                 write_or_die(fd, buf.buf, buf.len);

I.e. moving the starting and ending \n out of the message itself, the
surrounding whitespace doesn't seem like something the translators
need to modify, and if they were to trim it it looks like it would
break the output a bit.

      reply	other threads:[~2016-07-21 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 10:07 [PATCH] i18n: notes: mark comment for translation Vasco Almeida
2016-07-21 10:45 ` Æ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

  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='CACBZZX51K=D2gYbzKvJW3B5=bzxEGGFhOc6TkAfJkkpdYuEt0w@mail.gmail.com' \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=vascomalmeida@sapo.pt \
    /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).