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

Re: [PATCH] Internationalization of git-gui

From
Christian Stimming <stimming@tuhh.de>
Date
Jul 20, 2007, 08:56 UTC
Message-ID
<20070720105602.7dcm241ts0k0ww88@webmail.tu-harburg.de>
In-Reply-To
<20070720050455.GN32566@spearce.org>
Quoting "Shawn O. Pearce" <spearce@spearce.org>:
Show 15 quoted lines
> Brett Schwarz <brett_schwarz@yahoo.com> wrote:
>> This is a good idea. However, I assume the _ proc is just sugar. It
>> might be better to follow a more "standard" way for this, and just
>> import the msgcat namespace, and then you can just use [mc].
>>
>> package require msgcat
>> namespace import ::msgcat::*
>>   .
>>   .
>> .mbar add cascade -label [mc Repository] -menu .mbar.repository
>
> Not just better, I'd prefer it.  The proc name "_" is cute but
> is just too darn short.  I would much prefer to use "mc" and just
> say that "mc" in all of git-gui's namespaces is reserved for the
> message catalog

I used (and prefer) "_" because that's the standard function name for i18n'd strings when using gettext (talking about a "standard" way). In that case the convention from C simply carries over to tcl/tk, and programmers who have worked with gettext in C before, which uses _("some message"), directly apply what they already know. [mc ..], on the other hand, would be a tcl-only function name which doesn't give too much of a hint of what this function does, except for those programmers who happen to know that tcl's translation is done by a package called msgcat. One might rather consider something like [tr ...], for "translate", or even [i18n ...].

That being said, I'm rather agnostic on which proc name you really prefer. Just pick one.

Being a newcomer on this list, could you please explain to me how to proceed with the i18n patches so far? Do you want to have patches submitted after some further changes (which ones?) and/or in different formats? Do you prefer to have all changes in a smaller number of commit rather than split the way I did before? Should I wait for some more days/weeks/whatever until you or particular other developers have reviewed the patches? Thanks.

Christian
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 3 of 48 in “Re: [PATCH] Internationalization of git-gui”
  1. Brett SchwarzJul 19, 2007
  2. Shawn O. PearceJul 20, 2007
  3. Christian StimmingJul 20, 2007
  4. Shawn O. PearceJul 21, 2007
  5. Christian StimmingJul 21, 2007
  6. Shawn O. PearceJul 21, 2007
  7. Christian StimmingJul 21, 2007
  8. Christian StimmingJul 21, 2007
  9. Christian StimmingJul 21, 2007
  10. Christian StimmingJul 21, 2007
  11. Christian StimmingJul 21, 2007
  12. David KastrupJul 21, 2007
  13. Simon 'corecode' SchubertJul 21, 2007
  14. David KastrupJul 21, 2007
  15. Christian StimmingJul 21, 2007
  16. Christian StimmingJul 21, 2007
  17. David KastrupJul 21, 2007
  18. Christian StimmingJul 22, 2007
  19. Edgar ToernigJul 22, 2007
  20. Christian StimmingJul 23, 2007
  21. David KastrupJul 21, 2007
  22. Shawn O. PearceJul 22, 2007
  23. Junio C HamanoJul 22, 2007
  24. Christian StimmingJul 22, 2007
  25. Johannes SchindelinJul 22, 2007
  26. Christian StimmingJul 22, 2007
  27. Johannes SchindelinJul 22, 2007
  28. Shawn O. PearceJul 22, 2007
  29. Christian StimmingJul 22, 2007
  30. Johannes SchindelinJul 21, 2007
  31. Junio C HamanoJul 21, 2007
  32. Christian StimmingJul 21, 2007
  33. Johannes SchindelinJul 21, 2007
  34. Junio C HamanoJul 21, 2007
  35. Johannes SchindelinJul 21, 2007
  36. Christian StimmingJul 22, 2007
  37. Johannes SchindelinJul 22, 2007
  38. Add glossary that can be converted into a po file for each language.Christian Stimming, Jul 23, 2007
  39. Junio C HamanoJul 24, 2007
  40. Junio C HamanoJul 24, 2007
  41. Christian StimmingJul 24, 2007
  42. Johannes SchindelinJul 21, 2007
  43. Junio C HamanoJul 21, 2007
  44. Johannes SchindelinJul 21, 2007
  45. Shawn O. PearceJul 22, 2007
  46. Christian StimmingJul 23, 2007
  47. Shawn O. PearceJul 24, 2007
  48. Christian StimmingJul 20, 2007

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.