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

Re: [PATCH 2/2] i18n translate builtin warning, error, usage, fatal messages

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 5, 2014, 19:47 UTC
Message-ID
<xmqq4mwlrgrl.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1409943445-12283-3-git-send-email-sandy.carter@savoirfairelinux.com>
Sandy Carter <sandy.carter@savoirfairelinux.com> writes:
Show 5 quoted lines
> Allow warnings, errors, usage and fatal messages to be translated to user
> when checking out a ambiguous refname for example
>
> Signed-off-by: Sandy Carter <sandy.carter@savoirfairelinux.com>
> ---

Hmmmm. Doesn't this break the plumbing commands whose messages are meant to be matched and interpreted by scripts?

Show 36 quoted lines
>  usage.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/usage.c b/usage.c
> index ed14645..24a450e 100644
> --- a/usage.c
> +++ b/usage.c
> @@ -27,24 +27,24 @@ void vwritef(int fd, const char *prefix, const char *err, va_list params)
>  
>  static NORETURN void usage_builtin(const char *err, va_list params)
>  {
> -	vreportf("usage: ", err, params);
> +	vreportf(_("usage: "), err, params);
>  	exit(129);
>  }
>  
>  static NORETURN void die_builtin(const char *err, va_list params)
>  {
> -	vreportf("fatal: ", err, params);
> +	vreportf(_("fatal: "), err, params);
>  	exit(128);
>  }
>  
>  static void error_builtin(const char *err, va_list params)
>  {
> -	vreportf("error: ", err, params);
> +	vreportf(_("error: "), err, params);
>  }
>  
>  static void warn_builtin(const char *warn, va_list params)
>  {
> -	vreportf("warning: ", warn, params);
> +	vreportf(_("warning: "), warn, params);
>  }
>  
>  static int die_is_recursing_builtin(void)
Previous: Sandy Carter
Message 4 of 4 in “Translations for ambiguous refname warning”
  1. 0/2 Translations for ambiguous refname warningSandy Carter, Sep 5, 2014
  2. 1/2 i18n: ambiguous refname message is not translatedSandy Carter, Sep 5, 2014
  3. 2/2 i18n translate builtin warning, error, usage, fatal messagesSandy Carter, Sep 5, 2014
  4. Junio C HamanoSep 5, 2014

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.