git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 1/2] describe: localize debug output fully

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Mar 17, 2017, 15:12 UTC
Message-ID
<105f48ad2ae1aa9c88ce6088e6b304294bec0835.1489763302.git.git@drmicha.warpmail.net>

git describe --debug localizes all debug messages but not the terms head, lightweight, annotated that it outputs for the candidates. Localize them, too.

Also, increase the width of that field to create room for the translated terms.

Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
Ralf: this is just the context for the following l10-de patch
 builtin/describe.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/builtin/describe.c b/builtin/describe.c
index 76c18059bf..1a760c16f9 100644
--- a/builtin/describe.c
+++ b/builtin/describe.c
@@ -49,7 +49,7 @@ struct commit_name {
 };
 
 static const char *prio_names[] = {
-	"head", "lightweight", "annotated",
+	N_("head"), N_("lightweight"), N_("annotated"),
 };
 
 static int commit_name_cmp(const struct commit_name *cn1,
@@ -396,8 +396,8 @@ static void describe(const char *arg, int last_one)
 	if (debug) {
 		for (cur_match = 0; cur_match < match_cnt; cur_match++) {
 			struct possible_tag *t = &all_matches[cur_match];
-			fprintf(stderr, " %-11s %8d %s\n",
-				prio_names[t->name->prio],
+			fprintf(stderr, " %-15s %8d %s\n",
+				_(prio_names[t->name->prio]),
 				t->depth, t->name->path);
 		}
 		fprintf(stderr, _("traversed %lu commits\n"), seen_commits);
-- 
2.12.0.484.g92f9ab2bc1
Next: Michael J Gruber
Message 1 of 7 in “describe: localize debug output fully”
  1. 1/2 describe: localize debug output fullyMichael J Gruber, Mar 17, 2017
  2. 2/2 l10n: de: translate describe debug termsMichael J Gruber, Mar 17, 2017
  3. Junio C HamanoMar 17, 2017
  4. 1/2 describe: localize debug output fullyMichael J Gruber, Mar 27, 2017
  5. 2/2 l10n: de: translate describe debug termsMichael J Gruber, Mar 27, 2017
  6. 0/2 describe: localize debug outputMichael J Gruber, Mar 27, 2017
  7. Junio C HamanoMar 27, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.