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

Re: [PATCH] Internationalization of git-gui

From
BSBrett Schwarz <brett_schwarz@yahoo.com>
Date
Jul 20, 2007, 18:15 UTC
Message-ID
<111363.1999.qm@web38911.mail.mud.yahoo.com>
[my apologies about top posting...my mail reader sucks]
Sure, I wasn't saying there would be for sure an advantage in re-using catalogs. That's why I said it *might* be worth looking into. Just a suggestion.
I agree that a glossary should be created first. That way, translators have a common set to work with.
Just a note about string substitution. msgcat has substitution built-in, so instead of this:
    .mbar.apple add command -label [format [_ "About %s"] [appname]] \
You can do this:
    .mbar.apple add command -label [_ "About %s" [appname]] \
Thanks,
    --brett
----- Original Message ----
From: Christian Stimming <stimming@tuhh.de>
To: Brett Schwarz <brett_schwarz@yahoo.com>
Cc: git@vger.kernel.org; Paul Mackerras <paulus@samba.org>; Shawn O. Pearce <spearce@spearce.org>
Sent: Friday, July 20, 2007 2:03:54 AM
Subject: Re: [PATCH] Internationalization of git-gui
Quoting Brett Schwarz <brett_schwarz@yahoo.com>:
> Also, if the message catalogs are in a common location, then it   
> might be worth looking into having gitk utilize these msg catalogs   
> as well.

You mean you suggest to re-use existing msg catalogs in addition to ones that are created on our own? Well, from the i18n coordination work in another project (gnucash) I wouldn't expect any noticable benefit from doing so. The re-usable parts of translations are rather limited, basically limited to the standard menu entries and some more single-word strings (Yes/No/Cancel...). But even then re-using other translations might already decrease the quality of your own translation, because other translators of packages might already have chosen a different translation for e.g. "Cancel". For that reason I strongly suggest using one single msg catalog for one single project, so that the translator is even able to make sure each word is translated into the same translation throughout the project.

(I also strongly suggest creating and translating a glossary of the important terms before starting to translate the msg catalog itself, but that's a different issue.)

> p.s. the frink tool (http://wiki.tcl.tk/2611) is supposed to be able  
>  to convert -text and -label switches to use msgcat...it might be   
> worth looking into, instead of manually editing git-gui/gitk

Thanks for the pointer. However, the -text and -label switches can be found and edited rather easily by keyboard macros and such. More important than this are some changes that are necessary in order to obtain strings that are actually translatable, such as

-    .mbar.apple add command -label "About [appname]" \
+    .mbar.apple add command -label [format [_ "About %s"] [appname]] \
and you will agree those can only be done manually anyway.
Christian
      ____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect.  Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 
Message 1 of 1 in “Re: [PATCH] Internationalization of git-gui”
  1. Brett SchwarzJul 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.