{"thread":{"id":"9734","subject":"git-gui i18n status?","startedAt":"2007-09-01T04:29:24Z","lastAt":"2007-09-17T09:04:06Z","messageCount":11,"participants":["Shawn O. Pearce","Johannes Schindelin","Junio C Hamano","Michele Ballabio","Christian Stimming"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"52121","messageId":"20070901042924.GE18160@spearce.org","threadId":"9734","inReplyTo":null,"subject":"git-gui i18n status?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-09-01T04:29:24Z","receivedAt":"2007-09-01T04:29:24Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Now that git-gui 0.8.2 is out and git 1.5.3 is just around the corner\nI am starting to think about bringing the git-gui i18n work into the\nmain git-gui tree, so we can start working from a common codebase.\n\nLooking at the repository on repo.or.cz it looks like it needs to\nbe merged/rebased onto 0.8.2. There is a trivial merge conflict,\nbut there are some more subtle ones caused by the movement of\nthe library directory initialization down lower in git-gui.sh.\nFor example translations won't be initialized if we have an issue\nwith the output of git-version and want to prompt the user.\n\nWhat is the current plan? Should I be looking at the master branch\nof git://repo.or.cz/git-gui/git-gui-i18n.git for pulling? Or are\nfolks expecting that this series will be cleaned up before I pull it?\n\n-- \nShawn.\n"},{"id":"52157","messageId":"Pine.LNX.4.64.0709020003480.28586@racer.site","threadId":"9734","inReplyTo":"20070901042924.GE18160@spearce.org","subject":"Re: git-gui i18n status?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-09-01T23:42:00Z","receivedAt":"2007-09-01T23:42:00Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\n[Cc'ed all contributors. I mean, the real contributors, not just those \nwith cheap talk ;-)]\n\nOn Sat, 1 Sep 2007, Shawn O. Pearce wrote:\n\n> Now that git-gui 0.8.2 is out and git 1.5.3 is just around the corner I \n> am starting to think about bringing the git-gui i18n work into the main \n> git-gui tree, so we can start working from a common codebase.\n\nYes.\n\n> Looking at the repository on repo.or.cz it looks like it needs to be \n> merged/rebased onto 0.8.2. There is a trivial merge conflict, but there \n> are some more subtle ones caused by the movement of the library \n> directory initialization down lower in git-gui.sh. For example \n> translations won't be initialized if we have an issue with the output of \n> git-version and want to prompt the user.\n\nHmm. I am not enough involved in i18n stuff to form a proper opinion \nhere... Do you suggest to move the initialisation earlier?\n\n> What is the current plan? Should I be looking at the master branch of \n> git://repo.or.cz/git-gui/git-gui-i18n.git for pulling? Or are folks \n> expecting that this series will be cleaned up before I pull it?\n\nMy plan is to put out a cleaned up patch series:\n\n- Christian's patches, consolidated, to\n\n\t- Makefile rules for translation\n\t- Infrastructure in the source (basically adding [mc ...] \n\t everywhere, and initialising msgcat)\n\t- po/git-gui.pot\n\t- glossary\n\nThen I'd like to prepare consolidated patches for the individual \nlanguages, attributed to the author where unique, and to Nanako for \nJapanese (mentioning help from Junio), and to Paolo (mentioning help from \nMichele).\n\nJunio, Michele, is that attribution enough for you?\n\nAll these patches will go through the mailing list, so that people can \ncomment and suggest improvements.\n\nI'll also try to bug Christian into looking through the output of\n\n\tgit grep \\\" -- \\*.sh \\*.tcl | grep -vwe mc -e bind | less\n\nto make sure that we did not forget a string. ATM the output consists of \n300+ lines, so it is a bit boring. Maybe I can improve that command, \ntoo...\n\n(I see\n\n\t\"Invalid arguments to git-version\",\n\t\"Last arm of $type $name must be default\",\n\t\"git-version >= x\", \"git-gui: fatal error\",\n\t\"Cannot move to top of working directory:\\n\\n$err\",\n\t\"error: no icon for $w state={$state} $path\",\n\t\"error: no desc for state={$state} $path\",\n\t\"Unstaging [short_path $path] from commit\",\n\t\"Adding [short_path $path]\",\n\t\"fatal: cannot stat path $path: No such file or directory\",\n\t\"Possible environment issues exist.[...]\",\n\t\"Loading$cur_s annotations...\",\n\t\"Loading annotation...\",\n\t\"Author:\\t\",\n\t\"Committer:\\t\",\n\t\"Original File:\\t\",\n\t\"Originally By:\\n\",\n\t\"In File: \",\n\t\"Copied Or Moved Here By:\\n\",\n\t\"fatal: Cannot resolve $l_trck\",\n\t\"branch: Created from $new_expr\",\n\t\"merge $new_expr: Fast-forward\",\n\t\"Updating working directory to '[_name $this]'...\",\n\t\"Checked out '$name'.\",\n\t\"class $class already declared\",\n\t\"wrong # args: field name value?\",\n\t\"class $class is sealed (cannot add new fields)\",\n\t\"field $name already declared\",\n\t\"wrong # args: method name args body (ifdeleted body)?\",\n\t\"make_toplevel topvar winvar {options}\",\n\t\"unsupported option $name\",\n\t\"Commit $PARENT appears to be corrupt\",\n\t\"warning: Tcl does not support encoding '$enc'.\",\n\t\"This repository currently has approximately [...]\",\n\t\"Loading diff of [escape_path $path]...\",\n\t\"Unable to display [escape_path $path]\",\n\t\"* Binary file (not showing content).\",\n\t\"Unable to display [escape_path $path]\",\n\t\"error: Unhandled 3 way diff marker: {$op}\",\n\t\"error: Unhandled 2 way diff marker: {$op}\",\n\t\"Unstaging [short_path $current_diff_path] from commit\",\n\t\"Adding [short_path $current_diff_path]\", and\n\t\"The following branches are not completely merged into [...]\",\n\nbut I could have missed some, and it is possible some do not need [mc \n...].)\n\nCiao,\nDscho\n"},{"id":"52162","messageId":"7vtzqdriec.fsf@gitster.siamese.dyndns.org","threadId":"9734","inReplyTo":"Pine.LNX.4.64.0709020003480.28586@racer.site","subject":"Re: git-gui i18n status?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-09-02T01:00:11Z","receivedAt":"2007-09-02T01:00:11Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin writes:\n\n> Then I'd like to prepare consolidated patches for the individual \n> languages, attributed to the author where unique, and to Nanako for \n> Japanese (mentioning help from Junio), and to Paolo (mentioning help from \n> Michele).\n>\n> Junio, Michele, is that attribution enough for you?\n\nI am just one of those with cheap talk -- no objection from me.\n"},{"id":"52163","messageId":"20070902014242.GJ18160@spearce.org","threadId":"9734","inReplyTo":"Pine.LNX.4.64.0709020003480.28586@racer.site","subject":"Re: git-gui i18n status?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-09-02T01:42:42Z","receivedAt":"2007-09-02T01:42:42Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Johannes Schindelin wrote:\n> On Sat, 1 Sep 2007, Shawn O. Pearce wrote:\n> > Looking at the repository on repo.or.cz it looks like it needs to be \n> > merged/rebased onto 0.8.2. There is a trivial merge conflict, but there \n> > are some more subtle ones caused by the movement of the library \n> > directory initialization down lower in git-gui.sh. For example \n> > translations won't be initialized if we have an issue with the output of \n> > git-version and want to prompt the user.\n> \n> Hmm. I am not enough involved in i18n stuff to form a proper opinion \n> here... Do you suggest to move the initialisation earlier?\n\nYea, I think that's what we are going to have to do here. If we don't\nsetup the directory for the .msg files early enough than we cannot do\ntranslations through [mc]. Unfortunately that means we have to also\nbreak up the library initialization.\n\nI'll try to work up a patch that does this.\n \n> > What is the current plan? Should I be looking at the master branch of \n> > git://repo.or.cz/git-gui/git-gui-i18n.git for pulling? Or are folks \n> > expecting that this series will be cleaned up before I pull it?\n> \n> My plan is to put out a cleaned up patch series:\n...\n> All these patches will go through the mailing list, so that people can \n> comment and suggest improvements.\n\nOK, that works well for me. Nice clean series to apply.\n \n> I'll also try to bug Christian into looking through the output of\n> \n> \tgit grep \\\" -- \\*.sh \\*.tcl | grep -vwe mc -e bind | less\n> \n> to make sure that we did not forget a string. ATM the output consists of \n> 300+ lines, so it is a bit boring. Maybe I can improve that command, \n> too...\n\nSome of these are internal errors that should never be presented to\nan end-user, and some are for reflog entries. Here's a quick run\nthrough of these:\n\n D == internal error message (developer only)\n R == reflog message\n T == probably should be translated\n\n D \"Invalid arguments to git-version\",\n D \"Last arm of $type $name must be default\",\n D \"git-version >= x\",\n T \"git-gui: fatal error\",\n T \"Cannot move to top of working directory:\\n\\n$err\",\n D \"error: no icon for $w state={$state} $path\",\n D \"error: no desc for state={$state} $path\",\n T \"Unstaging [short_path $path] from commit\",\n T \"Adding [short_path $path]\",\n T \"fatal: cannot stat path $path: No such file or directory\",\n T \"Possible environment issues exist.[...]\",\n T \"Loading$cur_s annotations...\",\n T \"Loading annotation...\",\n T \"Author:\\t\",\n T \"Committer:\\t\",\n T \"Original File:\\t\",\n T \"Originally By:\\n\",\n T \"In File: \",\n T \"Copied Or Moved Here By:\\n\",\n T \"fatal: Cannot resolve $l_trck\",\n R \"branch: Created from $new_expr\",\n R \"merge $new_expr: Fast-forward\",\n T \"Updating working directory to '[_name $this]'...\",\n T \"Checked out '$name'.\",\n D \"class $class already declared\",\n D \"wrong # args: field name value?\",\n D \"class $class is sealed (cannot add new fields)\",\n D \"field $name already declared\",\n D \"wrong # args: method name args body (ifdeleted body)?\",\n D \"make_toplevel topvar winvar {options}\",\n D \"unsupported option $name\",\n T \"Commit $PARENT appears to be corrupt\",\n T \"warning: Tcl does not support encoding '$enc'.\",\n T \"This repository currently has approximately [...]\",\n T \"Loading diff of [escape_path $path]...\",\n T \"Unable to display [escape_path $path]\",\n T \"* Binary file (not showing content).\",\n T \"Unable to display [escape_path $path]\",\n D \"error: Unhandled 3 way diff marker: {$op}\",\n D \"error: Unhandled 2 way diff marker: {$op}\",\n T \"Unstaging [short_path $current_diff_path] from commit\",\n T \"Adding [short_path $current_diff_path]\", and\n T \"The following branches are not completely merged into [...]\",\n\nMessages that I marked as 'D' shouldn't ever be shown to an end-user\nas they represent a Tcl error from incorrect usage of an internal\nfunction. Translating these is fine but since it should never\nappear unless there is a serious bug in git-gui its probably not\nworth the translation effort.\n\nMessages marked as 'R' appear in the reflog for the corresponding\nbranch, etc. These are not currently translated by core Git so I\nam not sure if we should translate them in git-gui.\n\nMessages marked as 'T' above are most definately shown to\nthe end-user and should be translated, or at least offered for\ntranslation. I realize some terms have been kept in their English\nform even after translation as there isn't a good way to translate\nthem into every language.\n\n-- \nShawn.\n"},{"id":"52164","messageId":"20070902022444.GK18160@spearce.org","threadId":"9734","inReplyTo":"20070902014242.GJ18160@spearce.org","subject":"Re: git-gui i18n status?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-09-02T02:24:44Z","receivedAt":"2007-09-02T02:24:44Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"\"Shawn O. Pearce\" wrote:\n> Johannes Schindelin wrote:\n> > Hmm. I am not enough involved in i18n stuff to form a proper opinion \n> > here... Do you suggest to move the initialisation earlier?\n> \n> Yea, I think that's what we are going to have to do here. If we don't\n> setup the directory for the .msg files early enough than we cannot do\n> translations through [mc]. Unfortunately that means we have to also\n> break up the library initialization.\n> \n> I'll try to work up a patch that does this.\n\nThis two patch series is based on my current master (gitgui-0.8.2).\nIts also now in my pu branch.\n\n\n>From fc703c209d415fe20ad5551465b5b68b8ab8b046 Mon Sep 17 00:00:00 2001\nFrom: Shawn O. Pearce \nDate: Sat, 1 Sep 2007 21:58:29 -0400\nSubject: [PATCH] git-gui: Locate the library directory early during startup\n\nTo support a localized version of git-gui we need to locate the\nlibrary directory early so we can initialize Tcl's msgcat package\nto load translated messages from. This needs to occur before we\ndeclare our git-version proc so that errors related to locating\ngit or assessing its version can be reported to the end-user in\ntheir preferred language. However we have to keep the library\nloading until after git-version has been declared, otherwise we\nwill fail to start git-gui if we are using a fake tclIndex that\nwas generated by our Makefile.\n\nSigned-off-by: Shawn O. Pearce \n---\n git-gui.sh | 25 +++++++++++++++----------\n 1 files changed, 15 insertions(+), 10 deletions(-)\n\ndiff --git a/git-gui.sh b/git-gui.sh\nindex fa30ccc..4ea6e91 100755\n--- a/git-gui.sh\n+++ b/git-gui.sh\n@@ -44,6 +44,20 @@ if {[catch {package require Tcl 8.4} err]\n \n ######################################################################\n ##\n+## locate our library\n+\n+set oguilib {@@GITGUI_LIBDIR@@}\n+set oguirel {@@GITGUI_RELATIVE@@}\n+if {$oguirel eq {1}} {\n+\tset oguilib [file dirname [file dirname [file normalize $argv0]]]\n+\tset oguilib [file join $oguilib share git-gui lib]\n+} elseif {[string match @@* $oguirel]} {\n+\tset oguilib [file join [file dirname [file normalize $argv0]] lib]\n+}\n+unset oguirel\n+\n+######################################################################\n+##\n ## enable verbose loading?\n \n if {![catch {set _verbose $env(GITGUI_VERBOSE)}]} {\n@@ -595,15 +609,6 @@ You are using [git-version]:\n ##\n ## configure our library\n \n-set oguilib {@@GITGUI_LIBDIR@@}\n-set oguirel {@@GITGUI_RELATIVE@@}\n-if {$oguirel eq {1}} {\n-\tset oguilib [file dirname [file dirname [file normalize $argv0]]]\n-\tset oguilib [file join $oguilib share git-gui lib]\n-} elseif {[string match @@* $oguirel]} {\n-\tset oguilib [file join [file dirname [file normalize $argv0]] lib]\n-}\n-\n set idx [file join $oguilib tclIndex]\n if {[catch {set fd [open $idx r]} err]} {\n \tcatch {wm withdraw .}\n@@ -637,7 +642,7 @@ if {$idx ne {}} {\n } else {\n \tset auto_path [concat [list $oguilib] $auto_path]\n }\n-unset -nocomplain oguirel idx fd\n+unset -nocomplain idx fd\n \n ######################################################################\n ##\n-- \n1.5.3.rc7.30.g947ad2\n\n\n>From d4b0ccd931cc29f35e8f8493445af27ea72ed03e Mon Sep 17 00:00:00 2001\nFrom: Shawn O. Pearce \nDate: Sat, 1 Sep 2007 22:22:42 -0400\nSubject: [PATCH] git-gui: Initialize Tcl's msgcat library for internationalization\n\nTcl's msgcat library and corresponding mc procedure can locate a\ntranslated string for any user message, provided that it is first\ngiven a directory where the *.msg files are located containing the\ntranslations.\n\nDuring installation we will place the translations in lib/msgs/,\nso we need to inform msgcat of this location once we determine it\nduring startup. Our source code tree however will store all of\nthe translations within the po/ directory, so we need to special\ncase this variant.\n\nSigned-off-by: Shawn O. Pearce \n---\n git-gui.sh | 14 ++++++++++++++\n 1 files changed, 14 insertions(+), 0 deletions(-)\n\ndiff --git a/git-gui.sh b/git-gui.sh\nindex 4ea6e91..486d36e 100755\n--- a/git-gui.sh\n+++ b/git-gui.sh\n@@ -51,8 +51,12 @@ set oguirel {@@GITGUI_RELATIVE@@}\n if {$oguirel eq {1}} {\n \tset oguilib [file dirname [file dirname [file normalize $argv0]]]\n \tset oguilib [file join $oguilib share git-gui lib]\n+\tset oguimsg [file join $oguilib msgs]\n } elseif {[string match @@* $oguirel]} {\n \tset oguilib [file join [file dirname [file normalize $argv0]] lib]\n+\tset oguimsg [file join [file dirname [file normalize $argv0]] po]\n+} else {\n+\tset oguimsg [file join $oguilib msgs]\n }\n unset oguirel\n \n@@ -76,6 +80,16 @@ if {![catch {set _verbose $env(GITGUI_VERBOSE)}]} {\n \n ######################################################################\n ##\n+## Internationalization (i18n) through msgcat and gettext. See\n+## http://www.gnu.org/software/gettext/manual/html_node/Tcl.html\n+\n+package require msgcat\n+namespace import ::msgcat::mc\n+::msgcat::mcload $oguimsg\n+unset oguimsg\n+\n+######################################################################\n+##\n ## read only globals\n \n set _appname [lindex [file split $argv0] end]\n-- \n1.5.3.rc7.30.g947ad2\n\n-- \nShawn.\n"},{"id":"52190","messageId":"Pine.LNX.4.64.0709021320230.28586@racer.site","threadId":"9734","inReplyTo":"20070902022444.GK18160@spearce.org","subject":"Re: git-gui i18n status?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-09-02T12:20:48Z","receivedAt":"2007-09-02T12:20:48Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 1 Sep 2007, Shawn O. Pearce wrote:\n\n> \"Shawn O. Pearce\" wrote:\n> > Johannes Schindelin wrote:\n> > > Hmm. I am not enough involved in i18n stuff to form a proper opinion \n> > > here... Do you suggest to move the initialisation earlier?\n> > \n> > Yea, I think that's what we are going to have to do here. If we don't\n> > setup the directory for the .msg files early enough than we cannot do\n> > translations through [mc]. Unfortunately that means we have to also\n> > break up the library initialization.\n> > \n> > I'll try to work up a patch that does this.\n> \n> This two patch series is based on my current master (gitgui-0.8.2).\n> Its also now in my pu branch.\n\nSound both good to me. Christian?\n\nCiao,\nDscho\n"},{"id":"52191","messageId":"Pine.LNX.4.64.0709021322130.28586@racer.site","threadId":"9734","inReplyTo":"20070902014242.GJ18160@spearce.org","subject":"Re: git-gui i18n status?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-09-02T12:29:00Z","receivedAt":"2007-09-02T12:29:00Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 1 Sep 2007, Shawn O. Pearce wrote:\n\n> Johannes Schindelin wrote:\n>\n> > I'll also try to bug Christian into looking through the output of\n> > \n> > \tgit grep \\\" -- \\*.sh \\*.tcl | grep -vwe mc -e bind | less\n> > \n> > to make sure that we did not forget a string. ATM the output consists \n> > of 300+ lines, so it is a bit boring. Maybe I can improve that \n> > command, too...\n\nI'll have a look at them; no need to have them in the initial i18n commit, \nright? Especially since the translations cannot contain them yet.\n\nCiao,\nDscho\n\nP.S.: I seem to remember that Christian is away, so maybe we should just \nmove forward. So I'll first prepare the patch series (minus the changes \nyou have in pu).\n"},{"id":"52212","messageId":"200709021617.40585.barra_cuda@katamail.com","threadId":"9734","inReplyTo":"Pine.LNX.4.64.0709020003480.28586@racer.site","subject":"Re: git-gui i18n status?","fromName":"Michele Ballabio","fromEmail":"barra_cuda@katamail.com","sentAt":"2007-09-02T14:17:40Z","receivedAt":"2007-09-02T14:17:40Z","isPatch":false,"sender":{"key":"barra_cuda@katamail.com","avatar":"https://avatars.githubusercontent.com/u/16371673?v=4"},"body":"On Sunday 02 September 2007, Johannes Schindelin wrote:\n> Then I'd like to prepare consolidated patches for the individual \n> languages, attributed to the author where unique, and to Nanako for \n> Japanese (mentioning help from Junio), and to Paolo (mentioning help from \n> Michele).\n> \n> Junio, Michele, is that attribution enough for you?\n\nThat's fine with me.\n"},{"id":"53185","messageId":"200709161403.50780.stimming@tuhh.de","threadId":"9734","inReplyTo":"Pine.LNX.4.64.0709021320230.28586@racer.site","subject":"Re: git-gui i18n status?","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2007-09-16T12:03:50Z","receivedAt":"2007-09-16T12:03:50Z","isPatch":false,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Hi Shawn et al.,\n\nAm Sonntag, 2. September 2007 14:20 schrieb Johannes Schindelin:\n> > > > Hmm. I am not enough involved in i18n stuff to form a proper opinion\n> > > > here... Do you suggest to move the initialisation earlier?\n> > >\n> > > Yea, I think that's what we are going to have to do here. If we don't\n> > > setup the directory for the .msg files early enough than we cannot do\n> > > translations through [mc]. Unfortunately that means we have to also\n> > > break up the library initialization.\n> > >\n> > > I'll try to work up a patch that does this.\n> >\n> > This two patch series is based on my current master (gitgui-0.8.2).\n> > Its also now in my pu branch.\n>\n> Sound both good to me. Christian?\n\nThanks for including the i18n framework and existing translations into the \nmaster of git-gui. I loosely watched the progress here, but due to other \ncommitments I cannot spend as much time on git-gui i18n as I initially \nthought. I'd happily update and polish the German translation, though (will \nsend other email for that), but I probably can't follow any of the ongoing \ni18n cleanup work.\n\nOne question came up when seeing the i18n code really in git-gui.git: How are \ntranslators supposed to submit new or updated translations? Is \ngit-gui-i18n.git of any use anymore? This doesn't seem so. Should updated \ntranslations just be submitted by email to git@vger? In any case, the \ninstructions in po/README should probably be updated to explain the \nrecommended way of submitting translation updates. \n\nOh, and po/git-gui.pot should probably be updated to reflect the latest string \nadditions and changes. \n\nThanks a lot.\n\nChristian\n"},{"id":"53248","messageId":"20070917032042.GF3099@spearce.org","threadId":"9734","inReplyTo":"200709161403.50780.stimming@tuhh.de","subject":"Re: git-gui i18n status?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-09-17T03:20:42Z","receivedAt":"2007-09-17T03:20:42Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Christian Stimming wrote:\n> One question came up when seeing the i18n code really in git-gui.git: How are \n> translators supposed to submit new or updated translations? Is \n> git-gui-i18n.git of any use anymore? This doesn't seem so. Should updated \n> translations just be submitted by email to git@vger? In any case, the \n> instructions in po/README should probably be updated to explain the \n> recommended way of submitting translation updates. \n\nI was sort of hoping Dscho would be able to answer that. ;-)\n\nI can play patch-monkey and apply things people send to the mailing\nlist. I'm also willing to pull from a tree if the commit history\nis clean and mergable. Since each language more or less stands\non its own in its own .po file translators may find it easier to\nemail patches. I dunno, I'm not a translator.\n \n> Oh, and po/git-gui.pot should probably be updated to reflect the latest string \n> additions and changes. \n\nYes. Dscho was looking at creating a custom diff filter for git\nthat would better handle showing diffs here. I was sort of waiting\nfor progress from that (if any) before doing the pot update. I also\nhave a lot of UI work that I wanted to do in the 0.9.x series and\nthose are likely to create/change the sets of messages we need\nto translate.\n\n-- \nShawn.\n"},{"id":"53276","messageId":"Pine.LNX.4.64.0709171002510.28586@racer.site","threadId":"9734","inReplyTo":"20070917032042.GF3099@spearce.org","subject":"Re: git-gui i18n status?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-09-17T09:04:06Z","receivedAt":"2007-09-17T09:04:06Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sun, 16 Sep 2007, Shawn O. Pearce wrote:\n\n> Christian Stimming wrote:\n>\n> > One question came up when seeing the i18n code really in git-gui.git: \n> > How are translators supposed to submit new or updated translations? Is \n> > git-gui-i18n.git of any use anymore? This doesn't seem so. Should \n> > updated translations just be submitted by email to git@vger? In any \n> > case, the instructions in po/README should probably be updated to \n> > explain the recommended way of submitting translation updates.\n> \n> I was sort of hoping Dscho would be able to answer that. ;-)\n\nHeh. Yeah, sorry... I got sidetracked with other stuff.\n\nWill try to find some time for i18n,\nDscho\n"}]}