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

[PATCH v2 0/4] status: allow label strings to be translated

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 12, 2014, 21:19 UTC
Message-ID
<1394659174-9143-1-git-send-email-gitster@pobox.com>

So here is my attempt to clean-up what Jonathan posted in $gmane/239537 as "how about this?" patch.

The first one (full label string) fixes up 3651e45c (wt-status: take the alignment burden off translators, 2013-11-05) to include colon back to translatable string again, while retaining its label alignment logic.

The second (extract the code) is taken from Jonathan's $gmane/239537 as a separate patch.

The third is essentially the remainder of Jonathan's $gmane/239537, with one small fix s/strlen/utf8_width/; to teach the code that shows unmerged paths the same label alignment logic Duy added in 3651e45c for the tracked paths, while retaining the "at least 20 columns" floor to avoid the churn to the tests.

And the last lifts the "at least 20 columns" floor.
Jonathan Nieder (2):
  wt-status: extract the code to compute width for labels
  wt-status: i18n of section labels
Junio C Hamano (2):
  wt-status: make full label string to be subject to l10n
  wt-status: lift the artificual "at least 20 columns" floor
 t/t7060-wtstatus.sh    |  14 +++---
 t/t7512-status-help.sh |  12 ++---
 wt-status.c            | 117 +++++++++++++++++++++++++++++++------------------
 3 files changed, 88 insertions(+), 55 deletions(-)
-- 
1.9.0-293-gd838d6f
Next: Junio C Hamano
Message 1 of 5 in “status: allow label strings to be translated”
  1. 0/4 status: allow label strings to be translatedJunio C Hamano, Mar 12, 2014
  2. 1/4 wt-status: make full label string to be subject to l10nJunio C Hamano, Mar 12, 2014
  3. 2/4 wt-status: extract the code to compute width for labelsJunio C Hamano, Mar 12, 2014
  4. 3/4 wt-status: i18n of section labelsJunio C Hamano, Mar 12, 2014
  5. 4/4 wt-status: lift the artificual "at least 20 columns" floorJunio C Hamano, Mar 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.