Quoting Brett Schwarz <brett_schwarz@xxxxxxxxx>:
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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
