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

Re: [PATCH] status merge: guarentee space between msg and path

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 12, 2014, 18:39 UTC
Message-ID
<xmqqeh27mfc5.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CACsJy8DvBVxtP_+qbcxL0J8D3iokGeMVW0jxFtZD=Jk_A=mwQg@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
Show 13 quoted lines
> On Wed, Mar 12, 2014 at 3:26 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> Sandy Carter <sandy.carter@savoirfairelinux.com> writes:
>>
>>> 3651e45c takes the colon out of the control of the translators.
>>
>> That is a separate bug we would need to address, then.  Duy Cc'ed.
>
> We went through this before
>
> http://thread.gmane.org/gmane.linux.debian.devel.bugs.general/1109239/focus=239560
>
> If the colon needs language specific treatment then it should be part
> of the translatable strings.

OK. So we should resurrect $gmane/239537 and adjust the codepath that was touched by 3651e45c to move the colon into translatable string?

What other places do we assume that colons are to immediately follow whatever human-readable text used as a label/heading, I wonder...

Previous: Duy NguyenNext: Sandy Carter
Message 6 of 10 in “status merge: guarentee space between msg and path”
  1. status merge: guarentee space between msg and pathSandy Carter, Mar 11, 2014
  2. Junio C HamanoMar 11, 2014
  3. Sandy CarterMar 11, 2014
  4. Junio C HamanoMar 11, 2014
  5. Duy NguyenMar 11, 2014
  6. Junio C HamanoMar 12, 2014
  7. status merge: guarentee space between msg and pathSandy Carter, Mar 11, 2014
  8. Junio C HamanoMar 12, 2014
  9. Sandy CarterMar 12, 2014
  10. Junio C HamanoMar 12, 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.