{"thread":{"id":"9121","subject":"Re: [PATCH] Internationalization of git-gui","startedAt":"2007-07-20T18:15:03Z","lastAt":"2007-07-20T18:15:03Z","messageCount":1,"participants":["Brett Schwarz"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"47980","messageId":"111363.1999.qm@web38911.mail.mud.yahoo.com","threadId":"9121","inReplyTo":null,"subject":"Re: [PATCH] Internationalization of git-gui","fromName":"Brett Schwarz","fromEmail":"brett_schwarz@yahoo.com","sentAt":"2007-07-20T18:15:03Z","receivedAt":"2007-07-20T18:15:03Z","isPatch":true,"sender":{"key":"brett_schwarz@yahoo.com","avatar":null},"body":"[my apologies about top posting...my mail reader sucks]\n\n\nSure, 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.\n\nI agree that a glossary should be created first. That way, translators have a common set to work with.\n\nJust a note about string substitution. msgcat has substitution built-in, so instead of this:\n\n    .mbar.apple add command -label [format [_ \"About %s\"] [appname]] \\\n\nYou can do this:\n\n    .mbar.apple add command -label [_ \"About %s\" [appname]] \\\n\n\nThanks,\n    --brett\n\n\n----- Original Message ----\nFrom: Christian Stimming <stimming@tuhh.de>\nTo: Brett Schwarz <brett_schwarz@yahoo.com>\nCc: git@vger.kernel.org; Paul Mackerras <paulus@samba.org>; Shawn O. Pearce <spearce@spearce.org>\nSent: Friday, July 20, 2007 2:03:54 AM\nSubject: Re: [PATCH] Internationalization of git-gui\n\nQuoting Brett Schwarz <brett_schwarz@yahoo.com>:\n> Also, if the message catalogs are in a common location, then it   \n> might be worth looking into having gitk utilize these msg catalogs   \n> as well.\n\nYou mean you suggest to re-use existing msg catalogs in addition to  \nones that are created on our own? Well, from the i18n coordination  \nwork in another project (gnucash) I wouldn't expect any noticable  \nbenefit from doing so. The re-usable parts of translations are rather  \nlimited, basically limited to the standard menu entries and some more  \nsingle-word strings (Yes/No/Cancel...). But even then re-using other  \ntranslations might already decrease the quality of your own  \ntranslation, because other translators of packages might already have  \nchosen a different translation for e.g. \"Cancel\". For that reason I  \nstrongly suggest using one single msg catalog for one single project,  \nso that the translator is even able to make sure each word is  \ntranslated into the same translation throughout the project.\n\n(I also strongly suggest creating and translating a glossary of the  \nimportant terms before starting to translate the msg catalog itself,  \nbut that's a different issue.)\n\n> p.s. the frink tool (http://wiki.tcl.tk/2611) is supposed to be able  \n>  to convert -text and -label switches to use msgcat...it might be   \n> worth looking into, instead of manually editing git-gui/gitk\n\nThanks for the pointer. However, the -text and -label switches can be  \nfound and edited rather easily by keyboard macros and such. More  \nimportant than this are some changes that are necessary in order to  \nobtain strings that are actually translatable, such as\n\n-    .mbar.apple add command -label \"About [appname]\" \\\n+    .mbar.apple add command -label [format [_ \"About %s\"] [appname]] \\\n\nand you will agree those can only be done manually anyway.\n\nChristian\n\n\n\n\n\n      ____________________________________________________________________________________\nFussy? 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 \n"}]}