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

Re: [PATCH] Make a colon translatable

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 13, 2022, 16:48 UTC
Message-ID
<xmqqa6cp9bfo.fsf@gitster.g>
In-Reply-To
<10867692-7c2b-1f89-d575-3d9b6e696a24@free.fr>
Jean-Noël Avila <jn.avila@free.fr> writes:
> Just to chime in, I would tend to approve Julien's proposal, but with
> a reworded commit message, which should convey that the segment to 
> translate is not a full sentence.

Thanks. I think that is probably a sensible thing to do. The use of "%s:" (or "%s") is necessitated by the use of status_printf_ln() in

    status_printf_ln(s, c, "%s", what);

and if we had status_puts() instead, we wouldn't be having this discussion, as the line would have been

    status_puts(s, c, what);

and it is obvious that "what" (aka "label heading") wants to have colon after it.

Previous: Jean-Noël AvilaNext: Julien Palard
Message 6 of 8 in “Make a colon translatable”
  1. Make a colon translatableJulien Palard, Apr 11, 2022
  2. Junio C HamanoApr 11, 2022
  3. Ævar Arnfjörð BjarmasonApr 12, 2022
  4. Junio C HamanoApr 12, 2022
  5. Jean-Noël AvilaApr 13, 2022
  6. Junio C HamanoApr 13, 2022
  7. Julien PalardApr 12, 2022
  8. Junio C HamanoApr 12, 2022

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.