From: "D. Ben Knoble via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "D. Ben Knoble" <ben.knoble+github@gmail.com>,
"D. Ben Knoble" <ben.knoble+github@gmail.com>
Subject: [PATCH] i18n: mark more bundle.c strings for translation
Date: Thu, 13 Jul 2023 22:01:22 +0000 [thread overview]
Message-ID: <pull.1550.git.1689285683013.gitgitgadget@gmail.com> (raw)
From: "D. Ben Knoble" <ben.knoble+github@gmail.com>
These two messages were introduced in 8ba221e245 (bundle: output hash
information in 'verify', 2022-03-22) and 105c6f14ad (bundle: parse
filter capability, 2022-03-09) but never for translation.
Signed-off-by: D. Ben Knoble <ben.knoble+github@gmail.com>
---
i18n: mark more bundle.c strings for translation
I noticed that git bundle output contained some untranslated messages
for LC_ALL=fr_FR.UTF-8; in order to add translations for these messages,
they need to be marked for translation.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1550%2Fbenknoble%2Fbundle-translations-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1550/benknoble/bundle-translations-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1550
bundle.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/bundle.c b/bundle.c
index 8d5936c4212..a9744da255c 100644
--- a/bundle.c
+++ b/bundle.c
@@ -271,10 +271,10 @@ int verify_bundle(struct repository *r,
list_refs(r, 0, NULL);
}
- printf_ln("The bundle uses this hash algorithm: %s",
+ printf_ln(_("The bundle uses this hash algorithm: %s"),
header->hash_algo->name);
if (header->filter.choice)
- printf_ln("The bundle uses this filter: %s",
+ printf_ln(_("The bundle uses this filter: %s"),
list_objects_filter_spec(&header->filter));
}
cleanup:
base-commit: aa9166bcc0ba654fc21f198a30647ec087f733ed
--
gitgitgadget
next reply other threads:[~2023-07-13 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 22:01 D. Ben Knoble via GitGitGadget [this message]
2023-07-13 22:20 ` [PATCH] i18n: mark more bundle.c strings for translation 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=pull.1550.git.1689285683013.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=ben.knoble+github@gmail.com \
--cc=git@vger.kernel.org \
/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).