{"thread":{"id":"9241","subject":"[PATCH] git-gui wording suggestions","startedAt":"2007-07-26T09:19:02Z","lastAt":"2007-07-29T07:08:20Z","messageCount":6,"participants":["Christian Stimming","Shawn O. Pearce","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"48684","messageId":"20070726111902.xqkxcdlsbo8w4c8k@webmail.tu-harburg.de","threadId":"9241","inReplyTo":null,"subject":"[PATCH] git-gui wording suggestions","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2007-07-26T09:19:02Z","receivedAt":"2007-07-26T09:19:02Z","isPatch":true,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Unifiy wording to say \"to stage\" instead of \"to add\" always.\n\nCurrently, there is a mixup of saying \"staged changes\" vs. \"added  \nchanges\" in the git-gui program. You obviously decided to say \"staging  \narea\" instead of \"index\", hence \"add to staging area\"/\"stage\" instead  \nof \"add to index\".  I think this change is very good. Talking about  \nthe \"staging area\" explains the nature of this thingy much better and  \nmuch more unambiguous than \"index\".  Actually only after reading the  \nwording \"staging area\" I eventually understood what this \"index\" thing  \nis about... (Also, your chosen wording helps for creating a nice and  \nconsistent translation of that, but that's only an added bonus.)\n\nWith this patch I'd propose to talk every only about \"stage\" instead  \nof \"add\". IMHO that's just the logical conclusion of the above wording  \ndecision. What do you think?\n\n---\n  git-gui.sh          |    6 +++---\n  lib/checkout_op.tcl |    2 +-\n  lib/commit.tcl      |    4 ++--\n  lib/index.tcl       |    2 +-\n  lib/merge.tcl       |    2 +-\n  5 files changed, 8 insertions(+), 8 deletions(-)\n\ndiff --git a/git-gui.sh b/git-gui.sh\nindex 3536d38..fd8b4b4 100755\n--- a/git-gui.sh\n+++ b/git-gui.sh\n@@ -1824,12 +1824,12 @@ if {[is_enabled multicommit] || [is_enabled  \nsinglecommit]} {\n  \tlappend disable_on_lock \\\n  \t\t[list .mbar.commit entryconf [.mbar.commit index last] -state]\n\n-\t.mbar.commit add command -label [mc \"Add To Commit\"] \\\n+\t.mbar.commit add command -label [mc \"Stage To Commit\"] \\\n  \t\t-command do_add_selection\n  \tlappend disable_on_lock \\\n  \t\t[list .mbar.commit entryconf [.mbar.commit index last] -state]\n\n-\t.mbar.commit add command -label [mc \"Add Existing To Commit\"] \\\n+\t.mbar.commit add command -label [mc \"Stage Changed Files To Commit\"] \\\n  \t\t-command do_add_all \\\n  \t\t-accelerator $M1T-I\n  \tlappend disable_on_lock \\\n@@ -2180,7 +2180,7 @@ pack .vpane.lower.commarea.buttons.rescan -side  \ntop -fill x\n  lappend disable_on_lock \\\n  \t{.vpane.lower.commarea.buttons.rescan conf -state}\n\n-button .vpane.lower.commarea.buttons.incall -text [mc \"Add Existing\"] \\\n+button .vpane.lower.commarea.buttons.incall -text [mc \"Stage Changed\"] \\\n  \t-command do_add_all\n  pack .vpane.lower.commarea.buttons.incall -side top -fill x\n  lappend disable_on_lock \\\ndiff --git a/lib/checkout_op.tcl b/lib/checkout_op.tcl\nindex 25bf9cf..a2f2509 100644\n--- a/lib/checkout_op.tcl\n+++ b/lib/checkout_op.tcl\n@@ -247,7 +247,7 @@ method _checkout {} {\n  \tif {[lock_index checkout_op]} {\n  \t\tafter idle [cb _start_checkout]\n  \t} else {\n-\t\t_error $this [mc \"Index is already locked.\"]\n+\t\t_error $this [mc \"Staging area (index) is already locked.\"]\n  \t\tdelete_this\n  \t}\n  }\ndiff --git a/lib/commit.tcl b/lib/commit.tcl\nindex f60b11e..aa9110d 100644\n--- a/lib/commit.tcl\n+++ b/lib/commit.tcl\n@@ -153,7 +153,7 @@ The rescan will be automatically started now.\n  \t\tU? {\n  \t\t\terror_popup [mc \"Unmerged files cannot be committed.\n\n-File %s has merge conflicts.  You must resolve them and add the file  \nbefore committing.\n+File %s has merge conflicts.  You must resolve them and stage the  \nfile before committing.\n  \" [short_path $path]]\n  \t\t\tunlock_index\n  \t\t\treturn\n@@ -169,7 +169,7 @@ File %s cannot be committed by this program.\n  \tif {!$files_ready && ![string match *merge $curType]} {\n  \t\tinfo_popup [mc \"No changes to commit.\n\n-You must add at least 1 file before you can commit.\n+You must stage at least 1 file before you can commit.\n  \"]\n  \t\tunlock_index\n  \t\treturn\ndiff --git a/lib/index.tcl b/lib/index.tcl\nindex 38aa6ee..e91b864 100644\n--- a/lib/index.tcl\n+++ b/lib/index.tcl\n@@ -367,7 +367,7 @@ proc revert_helper {txt paths} {\n  \t\t\"[appname] ([reponame])\" \\\n  \t\t[mc \"%s\n\n-Any unadded changes will be permanently lost by the revert.\" $query] \\\n+Any unstaged changes will be permanently lost by the revert.\" $query] \\\n  \t\tquestion \\\n  \t\t1 \\\n  \t\t[mc \"Do Nothing\"] \\\ndiff --git a/lib/merge.tcl b/lib/merge.tcl\nindex 40e82a9..a6e8cc9 100644\n--- a/lib/merge.tcl\n+++ b/lib/merge.tcl\n@@ -46,7 +46,7 @@ The rescan will be automatically started now.\n\n  File %s has merge conflicts.\n\n-You must resolve them, add the file, and commit to complete the  \ncurrent merge.  Only then can you begin another merge.\n+You must resolve them, stage the file, and commit to complete the  \ncurrent merge.  Only then can you begin another merge.\n  \" [short_path $path]]\n  \t\t\tunlock_index\n  \t\t\treturn 0\n-- \n1.5.3.rc2.12.gbc280\n"},{"id":"48755","messageId":"20070727044009.GF20052@spearce.org","threadId":"9241","inReplyTo":"20070726111902.xqkxcdlsbo8w4c8k@webmail.tu-harburg.de","subject":"Re: [PATCH] git-gui wording suggestions","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-07-27T04:40:09Z","receivedAt":"2007-07-27T04:40:09Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Christian Stimming <stimming@tuhh.de> wrote:\n> Unifiy wording to say \"to stage\" instead of \"to add\" always.\n...\n> With this patch I'd propose to talk every only about \"stage\" instead  \n> of \"add\". IMHO that's just the logical conclusion of the above wording  \n> decision. What do you think?\n\nYes, I agree.  This is a necessary change, the current wording is\nvery confusing.  I would apply this earlier than the other i18n\nstuff, but this patch is written based upon the current i18n work.\n:-|\n\n> diff --git a/git-gui.sh b/git-gui.sh\n> index 3536d38..fd8b4b4 100755\n> --- a/git-gui.sh\n> +++ b/git-gui.sh\n> @@ -1824,12 +1824,12 @@ if {[is_enabled multicommit] || [is_enabled  \n> singlecommit]} {\n>   \tlappend disable_on_lock \\\n>   \t\t[list .mbar.commit entryconf [.mbar.commit index last] -state]\n> \n> -\t.mbar.commit add command -label [mc \"Add To Commit\"] \\\n> +\t.mbar.commit add command -label [mc \"Stage To Commit\"] \\\n>   \t\t-command do_add_selection\n>   \tlappend disable_on_lock \\\n>   \t\t[list .mbar.commit entryconf [.mbar.commit index last] -state]\n...\n\n-- \nShawn.\n"},{"id":"48759","messageId":"7vvec64elq.fsf@assigned-by-dhcp.cox.net","threadId":"9241","inReplyTo":"20070727044009.GF20052@spearce.org","subject":"Re: [PATCH] git-gui wording suggestions","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-07-27T05:09:37Z","receivedAt":"2007-07-27T05:09:37Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Shawn O. Pearce\" <spearce@spearce.org> writes:\n\n> Christian Stimming <stimming@tuhh.de> wrote:\n>> Unifiy wording to say \"to stage\" instead of \"to add\" always.\n> ...\n>> With this patch I'd propose to talk every only about \"stage\" instead  \n>> of \"add\". IMHO that's just the logical conclusion of the above wording  \n>> decision. What do you think?\n>\n> Yes, I agree.  This is a necessary change, the current wording is\n> very confusing.\n\nLooking at the expressions used in the application from the\npoint of view of translating the words to (or expressing the\nconcept in) another language helps finding more appropriate\nwording even in the original language.\n\n\"Add\" is a simple and nice word, but it is too broad, so \"to\nstage\" is an improvement.  The translated message for \"to stage\"\nfor Japanese we will probably end up choosing would translate\nback to English as \"Schedule for commit\".\n"},{"id":"48790","messageId":"20070727134219.wjkkfyg0g888ooss@webmail.tu-harburg.de","threadId":"9241","inReplyTo":"20070727044009.GF20052@spearce.org","subject":"Re: [PATCH] git-gui wording suggestions","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2007-07-27T11:42:19Z","receivedAt":"2007-07-27T11:42:19Z","isPatch":true,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Quoting \"Shawn O. Pearce\" <spearce@spearce.org>:\n>> Unifiy wording to say \"to stage\" instead of \"to add\" always.\n> ...\n>> With this patch I'd propose to talk every only about \"stage\" instead\n>> of \"add\". IMHO that's just the logical conclusion of the above wording\n>> decision. What do you think?\n>\n> Yes, I agree.  This is a necessary change, the current wording is\n> very confusing.  I would apply this earlier than the other i18n\n> stuff, but this patch is written based upon the current i18n work.\n> :-|\n\nWell, of course I have supplied this patch on top of the current i18n  \nmarkup work... on the other hand, back-porting the string changes to  \nthe non-i18n code means that the i18n changes themselves won't merge  \nanymore. For that reason I wouldn't suggest to apply this separately  \nfrom the i18n commits, unless you would want to adapt the i18n patches  \nas well.\n\nI'd rather suggest to consider the i18n changes rather soon by now,  \neven if the actual translations will be merged later. The [mc...]  \ncalls itself don't change the behaviour of the application, so I don't  \nthink it would be very risky do merge them sooner than later.  \nEventually, that's of course up to you.\n\nChristian\n"},{"id":"48933","messageId":"200707282217.10772.stimming@tuhh.de","threadId":"9241","inReplyTo":"861wevqz7d.fsf@lola.quinscape.zz","subject":"Re: [PATCH] git-gui.git: Wording suggestions, 2nd try","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2007-07-28T20:17:10Z","receivedAt":"2007-07-28T20:17:10Z","isPatch":true,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Unify wording to say \"to stage\" instead of \"to add\" always.\n\nAlso, the warning message when clicking \"Reset\" is adapted to\nthe wording \"Reset\" rather than a confusion \"Cancel commit?\".\n\nSigned-off-by: Christian Stimming <stimming@tuhh.de>\n---\nThis time, this patch is actually based on git-gui.git's master. If you want to, you can directly apply this regardless of i18n work that was deferred until later.\nThe last hunk in lib/merge.tcl looks a bit confusing; in preparation of i18n work, the previous message that inserted a single word into the long english sentence was already replaced by the i18n'able form of two completely different messages. But nevertheless the main point is that when clicking \"Reset\", the upcoming question should use the wording \"reset\", which it will do after this patch.\n\n git-gui.sh          |    6 +++---\n lib/checkout_op.tcl |    2 +-\n lib/commit.tcl      |    4 ++--\n lib/index.tcl       |    2 +-\n lib/merge.tcl       |   18 +++++++++++-------\n 5 files changed, 18 insertions(+), 14 deletions(-)\n\ndiff --git a/git-gui.sh b/git-gui.sh\nindex f87b955..d7fad46 100755\n--- a/git-gui.sh\n+++ b/git-gui.sh\n@@ -1827,12 +1827,12 @@ if {[is_enabled multicommit] || [is_enabled singlecommit]} {\n \tlappend disable_on_lock \\\n \t\t[list .mbar.commit entryconf [.mbar.commit index last] -state]\n \n-\t.mbar.commit add command -label {Add To Commit} \\\n+\t.mbar.commit add command -label {Stage To Commit} \\\n \t\t-command do_add_selection\n \tlappend disable_on_lock \\\n \t\t[list .mbar.commit entryconf [.mbar.commit index last] -state]\n \n-\t.mbar.commit add command -label {Add Tracked Files To Commit} \\\n+\t.mbar.commit add command -label {Stage Changed Files To Commit} \\\n \t\t-command do_add_all \\\n \t\t-accelerator $M1T-I\n \tlappend disable_on_lock \\\n@@ -2154,7 +2154,7 @@ pack .vpane.lower.commarea.buttons.rescan -side top -fill x\n lappend disable_on_lock \\\n \t{.vpane.lower.commarea.buttons.rescan conf -state}\n \n-button .vpane.lower.commarea.buttons.incall -text {Add Tracked} \\\n+button .vpane.lower.commarea.buttons.incall -text {Stage Changed} \\\n \t-command do_add_all\n pack .vpane.lower.commarea.buttons.incall -side top -fill x\n lappend disable_on_lock \\\ndiff --git a/lib/checkout_op.tcl b/lib/checkout_op.tcl\nindex 40cc73a..170f737 100644\n--- a/lib/checkout_op.tcl\n+++ b/lib/checkout_op.tcl\n@@ -248,7 +248,7 @@ method _checkout {} {\n \tif {[lock_index checkout_op]} {\n \t\tafter idle [cb _start_checkout]\n \t} else {\n-\t\t_error $this \"Index is already locked.\"\n+\t\t_error $this \"Staging area (index) is already locked.\"\n \t\tdelete_this\n \t}\n }\ndiff --git a/lib/commit.tcl b/lib/commit.tcl\nindex 1f5c2c3..f857a2f 100644\n--- a/lib/commit.tcl\n+++ b/lib/commit.tcl\n@@ -153,7 +153,7 @@ The rescan will be automatically started now.\n \t\tU? {\n \t\t\terror_popup \"Unmerged files cannot be committed.\n \n-File [short_path $path] has merge conflicts.  You must resolve them and add the file before committing.\n+File [short_path $path] has merge conflicts.  You must resolve them and stage the file before committing.\n \"\n \t\t\tunlock_index\n \t\t\treturn\n@@ -169,7 +169,7 @@ File [short_path $path] cannot be committed by this program.\n \tif {!$files_ready && ![string match *merge $curType]} {\n \t\tinfo_popup {No changes to commit.\n \n-You must add at least 1 file before you can commit.\n+You must stage at least 1 file before you can commit.\n }\n \t\tunlock_index\n \t\treturn\ndiff --git a/lib/index.tcl b/lib/index.tcl\nindex 3ea72e1..f47f929 100644\n--- a/lib/index.tcl\n+++ b/lib/index.tcl\n@@ -360,7 +360,7 @@ proc revert_helper {txt paths} {\n \t\t\"[appname] ([reponame])\" \\\n \t\t\"Revert changes in $s?\n \n-Any unadded changes will be permanently lost by the revert.\" \\\n+Any unstaged changes will be permanently lost by the revert.\" \\\n \t\tquestion \\\n \t\t1 \\\n \t\t{Do Nothing} \\\ndiff --git a/lib/merge.tcl b/lib/merge.tcl\nindex 148d859..f6a2df3 100644\n--- a/lib/merge.tcl\n+++ b/lib/merge.tcl\n@@ -45,7 +45,7 @@ The rescan will be automatically started now.\n \n File [short_path $path] has merge conflicts.\n \n-You must resolve them, add the file, and commit to complete the current merge.  Only then can you begin another merge.\n+You must resolve them, stage the file, and commit to complete the current merge.  Only then can you begin another merge.\n \"\n \t\t\tunlock_index\n \t\t\treturn 0\n@@ -219,16 +219,20 @@ You must finish amending this commit.\n \tif {![lock_index abort]} return\n \n \tif {[string match *merge* $commit_type]} {\n-\t\tset op merge\n+\t\tset op_question \"Abort merge?\n+\n+Aborting the current merge will cause *ALL* uncommitted changes to be lost.\n+\n+Continue with aborting the current merge?\"\n \t} else {\n-\t\tset op commit\n-\t}\n+\t\tset op_question \"Reset changes?\n \n-\tif {[ask_popup \"Abort $op?\n+Resetting the changes will cause *ALL* uncommitted changes to be lost.\n \n-Aborting the current $op will cause *ALL* uncommitted changes to be lost.\n+Continue with resetting the current changes?\"\n+\t}\n \n-Continue with aborting the current $op?\"] eq {yes}} {\n+\tif {[ask_popup $op_question] eq {yes}} {\n \t\tset fd [git_read read-tree --reset -u HEAD]\n \t\tfconfigure $fd -blocking 0 -translation binary\n \t\tfileevent $fd readable [namespace code [list _reset_wait $fd]]\n-- \n1.5.2\n"},{"id":"48957","messageId":"20070729070820.GK20052@spearce.org","threadId":"9241","inReplyTo":"200707282217.10772.stimming@tuhh.de","subject":"Re: [PATCH] git-gui.git: Wording suggestions, 2nd try","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-07-29T07:08:20Z","receivedAt":"2007-07-29T07:08:20Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Christian Stimming <stimming@tuhh.de> wrote:\n> Unify wording to say \"to stage\" instead of \"to add\" always.\n> \n> Also, the warning message when clicking \"Reset\" is adapted to\n> the wording \"Reset\" rather than a confusion \"Cancel commit?\".\n> \n> Signed-off-by: Christian Stimming <stimming@tuhh.de>\n> ---\n> This time, this patch is actually based on git-gui.git's master. If\n> you want to, you can directly apply this regardless of i18n work that\n> was deferred until later.  The last hunk in lib/merge.tcl looks a\n> bit confusing; in preparation of i18n work, the previous message\n> that inserted a single word into the long english sentence was\n> already replaced by the i18n'able form of two completely different\n> messages. But nevertheless the main point is that when clicking\n> \"Reset\", the upcoming question should use the wording \"reset\",\n> which it will do after this patch.\n\nThanks, I'm including this in 0.8.0 as I think it makes things\na lot clearer, at least for English speakers.  ;-)\n\nAs soon as git 1.5.3 ships I'll start work on 0.9.0, and I'm\nlooking to bringing the i18n work in as the first series of\nchanges for the 0.9.x series...\n \n-- \nShawn.\n"}]}