{"thread":{"id":"29595","subject":"Bulgarian translation of git","startedAt":"2012-02-10T12:26:59Z","lastAt":"2012-02-15T18:09:37Z","messageCount":12,"participants":["=?UTF-8?Q? Alexander_Shopov_(=D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=8A=D1=80_=D0=A8=D0=BE=D0=BF=D0=BE=D0=B2) ?=","Jiang Xin","Junio C Hamano","Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"184349","messageId":"75009f1d7c4aba4d62bb226ab122932c@192.168.122.10","threadId":"29595","inReplyTo":null,"subject":"Bulgarian translation of git","fromName":"=?UTF-8?Q? Alexander_Shopov_(=D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=8A=D1=80_=D0=A8=D0=BE=D0=BF=D0=BE=D0=B2) ?=","fromEmail":"lists@kambanaria.org","sentAt":"2012-02-10T12:26:59Z","receivedAt":"2012-02-10T12:26:59Z","isPatch":false,"sender":{"key":"lists@kambanaria.org","avatar":null},"body":"Hello,\n\nI am Alexander Shopov and would like to volunteer for the Bulgarian\ntranslation of git po file if no one else is doing this.\nHow should I contribute it back?\nVia this email list, via fork-push from github, or a patch?\n\nKind regards:\nal_shopov\n"},{"id":"184536","messageId":"CANYiYbGr3zN-kJwq_MCnttNZP6Cc0aj-fsZjd4V=4z+BA5TvUw@mail.gmail.com","threadId":"29595","inReplyTo":"75009f1d7c4aba4d62bb226ab122932c@192.168.122.10","subject":"Re: Bulgarian translation of git","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2012-02-13T02:46:14Z","receivedAt":"2012-02-13T02:46:14Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"Junio has a suggestion on how to contrib l10n for git, and you can see the\ndiscussion here: http://article.gmane.org/gmane.comp.version-control.git/189584.\n\nSeems that the suggested git-po repo has not been setup yet, so let me\nhave a try.\n\n1. Repositiry git-po is hosted on GitHub: https://github.com/gotgit/git-po/\n\n2. I made a commit on the maint branch with a initial version of 'po/git.pot'\n    https://github.com/gotgit/git-po/commit/4247a7a9d39e2a74ce1d58e5eb1f5e5d87977989\n\n3. As l10n coordinator for Chinese, I translate against the pot file, and\n    the translated po file 'po/zh_CN.po' is commited in my own branch:\nmaint-zh-cn.\n    You can find the commit in:\nhttps://github.com/gotgit/git-po/commits/maint-zh-cn\n\n4. I will merge the commit in branch maint-zh-cn back or other l10n\ncoordinators' contributes\n    to maint branch.\n\nI have a question, which version of po should be maintained? master\nbranch or maint branch.\n\n2012/2/10 \"Alexander Shopov (Александър Шопов)\" <lists@kambanaria.org>:\n> Hello,\n>\n> I am Alexander Shopov and would like to volunteer for the Bulgarian\n> translation of git po file if no one else is doing this.\n> How should I contribute it back?\n> Via this email list, via fork-push from github, or a patch?\n>\n> Kind regards:\n> al_shopov\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n\n\n\n-- \n蒋鑫\n\n北京群英汇信息技术有限公司\n邮件: worldhello.net@gmail.com\n网址: http://www.ossxp.com/\n博客: http://www.worldhello.net/\n微博: http://weibo.com/gotgit/\n电话: 010-51262007, 18601196889\n"},{"id":"184539","messageId":"7vy5s7idxb.fsf@alter.siamese.dyndns.org","threadId":"29595","inReplyTo":"CANYiYbGr3zN-kJwq_MCnttNZP6Cc0aj-fsZjd4V=4z+BA5TvUw@mail.gmail.com","subject":"Re: Bulgarian translation of git","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-02-13T03:56:48Z","receivedAt":"2012-02-13T03:56:48Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jiang Xin <worldhello.net@gmail.com> writes:\n\n> Junio has a suggestion on how to contrib l10n for git, and you can see the\n> discussion here: http://article.gmane.org/gmane.comp.version-control.git/189584.\n>\n> Seems that the suggested git-po repo has not been setup yet, so let me\n> have a try.\n>\n> 1. Repositiry git-po is hosted on GitHub: https://github.com/gotgit/git-po/\n>\n> 2. I made a commit on the maint branch with a initial version of 'po/git.pot'\n>     https://github.com/gotgit/git-po/commit/4247a7a9d39e2a74ce1d58e5eb1f5e5d87977989\n\nSomebody needs to eyeball this commit before anything else happens on top\nof it, so that if there is a glaring mistake it can be caught before it\nspreads to affect work by translators for various languages.\n\n\n> 3. As l10n coordinator for Chinese, I translate against the pot file, and\n>     the translated po file 'po/zh_CN.po' is commited in my own branch:\n> maint-zh-cn.\n>     You can find the commit in:\n> https://github.com/gotgit/git-po/commits/maint-zh-cn\n>\n> 4. I will merge the commit in branch maint-zh-cn back or other l10n\n> coordinators' contributes\n>     to maint branch.\n>\n> I have a question, which version of po should be maintained? master\n> branch or maint branch.\n\nI would say for this round the git-po repository and its pot file should\npick up whatever new translatable strings are added to 'master'.\n\nAfter this is merged in 1.7.10, we may want to maintain separate tracks,\nbut at this moment there is no point maintaining something mergeable to\n1.7.9.x maintenance track.\n"},{"id":"184553","messageId":"CANYiYbFYmGNE09fAeHL_uk+0s+yBapTs4BeGch7iCtWR_v9LXQ@mail.gmail.com","threadId":"29595","inReplyTo":"7vy5s7idxb.fsf@alter.siamese.dyndns.org","subject":"Re: Bulgarian translation of git","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2012-02-13T07:12:50Z","receivedAt":"2012-02-13T07:12:50Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2012/2/13 Junio C Hamano <gitster@pobox.com>:\n> Jiang Xin <worldhello.net@gmail.com> writes:\n>\n>> Junio has a suggestion on how to contrib l10n for git, and you can see the\n>> discussion here: http://article.gmane.org/gmane.comp.version-control.git/189584.\n>>\n>> Seems that the suggested git-po repo has not been setup yet, so let me\n>> have a try.\n>>\n>> 1. Repositiry git-po is hosted on GitHub: https://github.com/gotgit/git-po/\n>>\n>> 2. I made a commit on the maint branch with a initial version of 'po/git.pot'\n>>     https://github.com/gotgit/git-po/commit/4247a7a9d39e2a74ce1d58e5eb1f5e5d87977989\n\nThis commit is based on current maint branch. Since the translated po files will\nfirst in 1.7.10, so the initial pot file should be generated from master branch.\nThe pot file from the master branch has 10 new messages than from the maint\nbranch.\n\nFor clarity, I removed the maint and other branches except the master branch,\nand made a new commit.\n\n> Somebody needs to eyeball this commit before anything else happens on top\n> of it, so that if there is a glaring mistake it can be caught before it\n> spreads to affect work by translators for various languages.\n\nSo please check this commit with the updated pot file:\nhttps://github.com/gotgit/git-po/commit/816049b7ec0e5f452c77a4c4e71e2cb40a0ccb45\nPlease note In this commit I removed one line from the 'po/.gitignore' file.\n\nAs a translater for Chinese, I also made a commit with the translated po file\n'po/zh_CN.po' in branch master-zh-cn (merged back to master branch).\n\n>>\n>> I have a question, which version of po should be maintained? master\n>> branch or maint branch.\n>\n> I would say for this round the git-po repository and its pot file should\n> pick up whatever new translatable strings are added to 'master'.\n>\n> After this is merged in 1.7.10, we may want to maintain separate tracks,\n> but at this moment there is no point maintaining something mergeable to\n> 1.7.9.x maintenance track.\n>\n\n\n-- \nJiang Xin\n"},{"id":"184554","messageId":"7v8vk7gnqf.fsf@alter.siamese.dyndns.org","threadId":"29595","inReplyTo":"CANYiYbFYmGNE09fAeHL_uk+0s+yBapTs4BeGch7iCtWR_v9LXQ@mail.gmail.com","subject":"Re: Bulgarian translation of git","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-02-13T08:07:52Z","receivedAt":"2012-02-13T08:07:52Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jiang Xin <worldhello.net@gmail.com> writes:\n\n>> Somebody needs to eyeball this commit before anything else happens on top\n>> of it, so that if there is a glaring mistake it can be caught before it\n>> spreads to affect work by translators for various languages.\n>\n> So please check this commit with the updated pot file:\n> https://github.com/gotgit/git-po/commit/816049b7ec0e5f452c77a4c4e71e2cb40a0ccb45\n> Please note In this commit I removed one line from the 'po/.gitignore' file.\n\nThanks.\n\nAs far as I can tell, this adds git.pot while removes the entry to remove\nit from po/.gitignore (because now it is a tracked file), but there is no\ndescription on how this file was generated in the log message.\n\nPlease give a short description to the effect that it was mechanically\ncreated by running xgettext on the sources as of b6b3b6a (Update draft\nrelease notes to 1.7.10, 2012-02-10), or something like that.\n\nOther than that, I do not immediately see anything objectionable in this\ncommit; I would still appreciate an extra set of eyeballs or two from\npeople who have worked on gitk and/or git-gui i18n/l10n infrastructure in\nthe past, just in case I forgot to check some obvious/trivial gotchas.\n\nI am also Cc'ing people who participated in git-gui and gitk l10n with\nmore than a couple of commits to their po/ part, found by:\n\n    $ cd git-gui/po &&\n      git rev-list --parents HEAD . |\n      while read commit parent\n      do\n        git log --pretty=short $parent..$commit^2 -- :/po\n      done | git shortlog -n -e\n\n(same for gitk-git)\n\n> As a translater for Chinese, I also made a commit with the translated po file\n> 'po/zh_CN.po' in branch master-zh-cn (merged back to master branch).\n\nThanks.\n"},{"id":"184555","messageId":"CANYiYbHHqCu5yUzPxaGD238jpM6XsP6=-uC1c_x+Q=OsunBSVA@mail.gmail.com","threadId":"29595","inReplyTo":"7v8vk7gnqf.fsf@alter.siamese.dyndns.org","subject":"Re: Bulgarian translation of git","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2012-02-13T08:52:40Z","receivedAt":"2012-02-13T08:52:40Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2012/2/13 Junio C Hamano <gitster@pobox.com>:\n> Jiang Xin <worldhello.net@gmail.com> writes:\n>\n>>> Somebody needs to eyeball this commit before anything else happens on top\n>>> of it, so that if there is a glaring mistake it can be caught before it\n>>> spreads to affect work by translators for various languages.\n>>\n>> So please check this commit with the updated pot file:\n>> ...\n\nPlease check this commit with the updated pot file:\nhttps://github.com/gotgit/git-po/commit/master%5E\n( The commit with the amended commit message can be access using\nthe above URL, no longer how this commit is ammended latter.)\n\n> As far as I can tell, this adds git.pot while removes the entry to remove\n> it from po/.gitignore (because now it is a tracked file), but there is no\n> description on how this file was generated in the log message.\n>\n> Please give a short description to the effect that it was mechanically\n> created by running xgettext on the sources as of b6b3b6a (Update draft\n> release notes to 1.7.10, 2012-02-10), or something like that.\n\nI add a prefix 'l10n:' to the new amended commit log, is it OK?\n\n$ git show --stat master^\ncommit b55102542911326e8191500ff6f53a2e1d52e504\nAuthor: Jiang Xin <worldhello.net@gmail.com>\nDate:   Mon Feb 13 14:37:59 2012 +0800\n\n    l10n: initial git.pot for 1.7.10 upcoming release\n\n    The file 'po/git.pot' is generated using the command 'make pot'\n    against git v1.7.9-209-gb6b3b (Update draft release notes to 1.7.10).\n\n    Also removed the entry po/git.pot from po/.gitignore, since it is a\n    tracked file.\n\n    Signed-off-by: Jiang Xin <worldhello.net@gmail.com>\n\n po/.gitignore |    1 -\n po/git.pot    | 3431 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n 2 files changed, 3431 insertions(+), 1 deletions(-)\n\n\n-- \nJiang Xin\n"},{"id":"184565","messageId":"20120213133957.GA4838@burratino","threadId":"29595","inReplyTo":"7vy5s7idxb.fsf@alter.siamese.dyndns.org","subject":"Re: Bulgarian translation of git","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2012-02-13T14:00:36Z","receivedAt":"2012-02-13T14:00:36Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Junio C Hamano wrote:\n> Jiang Xin <worldhello.net@gmail.com> writes:\n\n>> I have a question, which version of po should be maintained? master\n>> branch or maint branch.\n>\n> I would say for this round the git-po repository and its pot file should\n> pick up whatever new translatable strings are added to 'master'.\n>\n> After this is merged in 1.7.10, we may want to maintain separate tracks,\n> but at this moment there is no point maintaining something mergeable to\n> 1.7.9.x maintenance track.\n\nI wonder if there's a simple to ask the gettext tools to make a po\ntemplate including strings from both 'maint' and 'master'.  (Hackish way\ndemonstrated below.)\n\nHopefully that would make it easier for translators to keep both\ntracks well maintained at the same time.  If a problem in the\ntranslation of a string shared by 'master' and 'maint' is only noticed\nwhile working on 'master', there would be no need to go through the\n\"switch branches; make the change; switch back; merge\" dance.\n\nWhat do you think?\nJonathan\n\ndiff --git i/Makefile w/Makefile\nindex 1e91b19c..5dbc6205 100644\n--- i/Makefile\n+++ w/Makefile\n@@ -2103,7 +2103,8 @@ LOCALIZED_C := $(C_OBJ:o=c)\n LOCALIZED_SH := $(SCRIPT_SH)\n \n po/git.pot: $(LOCALIZED_C)\n-\t$(QUIET_XGETTEXT)$(XGETTEXT) -o$@+ $(XGETTEXT_FLAGS_C) $(LOCALIZED_C)\n+\tcp $@ $@+\n+\t$(QUIET_XGETTEXT)$(XGETTEXT) -o$@+ --join-existing $(XGETTEXT_FLAGS_C) $(LOCALIZED_C)\n \t$(QUIET_XGETTEXT)$(XGETTEXT) -o$@+ --join-existing $(XGETTEXT_FLAGS_SH) \\\n \t\t$(LOCALIZED_SH)\n \tmv $@+ $@\n"},{"id":"184570","messageId":"CANYiYbHkbUvL-d4M0iOyE5F-6rM=swk_knGEFTr9HGBK6T9UDg@mail.gmail.com","threadId":"29595","inReplyTo":"20120213133957.GA4838@burratino","subject":"Re: Bulgarian translation of git","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2012-02-13T15:43:45Z","receivedAt":"2012-02-13T15:43:45Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2012/2/13 Jonathan Nieder <jrnieder@gmail.com>:\n> I wonder if there's a simple to ask the gettext tools to make a po\n> template including strings from both 'maint' and 'master'.  (Hackish way\n> demonstrated below.)\n>\n> Hopefully that would make it easier for translators to keep both\n> tracks well maintained at the same time.  If a problem in the\n> translation of a string shared by 'master' and 'maint' is only noticed\n> while working on 'master', there would be no need to go through the\n> \"switch branches; make the change; switch back; merge\" dance.\n>\n> What do you think?\n\nTranslators on a new language may not like this. Translating the obsolete\nmessages in pot file is boring and waste of time.\n\n>  po/git.pot: $(LOCALIZED_C)\n> -       $(QUIET_XGETTEXT)$(XGETTEXT) -o$@+ $(XGETTEXT_FLAGS_C) $(LOCALIZED_C)\n> +       cp $@ $@+\n\nFailed if po/git.pot does not exist. touch one first?\n\n> +       $(QUIET_XGETTEXT)$(XGETTEXT) -o$@+ --join-existing $(XGETTEXT_FLAGS_C) $(LOCALIZED_C)\n>        $(QUIET_XGETTEXT)$(XGETTEXT) -o$@+ --join-existing $(XGETTEXT_FLAGS_SH) \\\n>                $(LOCALIZED_SH)\n>        mv $@+ $@\n\n-- \nJiang Xin\n"},{"id":"184571","messageId":"20120213155623.GH4140@burratino","threadId":"29595","inReplyTo":"CANYiYbHkbUvL-d4M0iOyE5F-6rM=swk_knGEFTr9HGBK6T9UDg@mail.gmail.com","subject":"Re: Bulgarian translation of git","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2012-02-13T15:56:23Z","receivedAt":"2012-02-13T15:56:23Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Jiang Xin wrote:\n> 2012/2/13 Jonathan Nieder <jrnieder@gmail.com>:\n\n>> I wonder if there's a simple to ask the gettext tools to make a po\n>> template including strings from both 'maint' and 'master'.  (Hackish way\n>> demonstrated below.)\n>>\n>> Hopefully that would make it easier for translators to keep both\n>> tracks well maintained at the same time.\n[...]\n>> What do you think?\n>\n> Translators on a new language may not like this. Translating the obsolete\n> messages in pot file is boring and waste of time.\n\nRight, doing this for real require somehow removing stale messages,\ntoo, so the pot file would only contain messages from actively\nmaintained releases (the tip of 'master' and 'maint').\n\nWill experiment privately a little more.\n"},{"id":"184583","messageId":"7vehtyftwf.fsf@alter.siamese.dyndns.org","threadId":"29595","inReplyTo":"20120213133957.GA4838@burratino","subject":"Re: Bulgarian translation of git","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-02-13T18:52:16Z","receivedAt":"2012-02-13T18:52:16Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jonathan Nieder <jrnieder@gmail.com> writes:\n\n> Hopefully that would make it easier for translators to keep both\n> tracks well maintained at the same time.\n\nI somehow think it is not such a big deal if l10n messages are not\nmaintained for maintenance tracks at all, actually, given that our cycles\nfor the master track have been 8-10 weeks long, which is not a long time\nto wait, compared to 5 years people survived without any ;-).\n"},{"id":"184743","messageId":"CANYiYbF-M0SLP=XFkD+nEVRth05pf3hohPLyqQ75qjtNGqANMA@mail.gmail.com","threadId":"29595","inReplyTo":"7vehtyftwf.fsf@alter.siamese.dyndns.org","subject":"Re: Bulgarian translation of git","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2012-02-15T03:28:28Z","receivedAt":"2012-02-15T03:28:28Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"I squash the following in the pot initial commit, and update the commit log.\ncommit:  https://github.com/gotgit/git-po/commit/master%5E\n\ndiff --git a/Makefile b/Makefile\nindex 87fb3..88268 100644\n--- a/Makefile\n+++ b/Makefile\n@@ -2576,7 +2576,6 @@ dist-doc:\n\n distclean: clean\n        $(RM) configure\n-       $(RM) po/git.pot\n\n clean:\n        $(RM) *.o block-sha1/*.o ppc/*.o compat/*.o compat/*/*.o\nxdiff/*.o vcs-svn/*.o \\\n\n\n2012/2/14 Junio C Hamano <gitster@pobox.com>:\n> Jonathan Nieder <jrnieder@gmail.com> writes:\n>\n>> Hopefully that would make it easier for translators to keep both\n>> tracks well maintained at the same time.\n>\n> I somehow think it is not such a big deal if l10n messages are not\n> maintained for maintenance tracks at all, actually, given that our cycles\n> for the master track have been 8-10 weeks long, which is not a long time\n> to wait, compared to 5 years people survived without any ;-).\n>\n\n\n\n-- \n蒋鑫\n\n北京群英汇信息技术有限公司\n邮件: worldhello.net@gmail.com\n网址: http://www.ossxp.com/\n博客: http://www.worldhello.net/\n微博: http://weibo.com/gotgit/\n电话: 010-51262007, 18601196889\n"},{"id":"184775","messageId":"7vehtw0xzy.fsf@alter.siamese.dyndns.org","threadId":"29595","inReplyTo":"CANYiYbF-M0SLP=XFkD+nEVRth05pf3hohPLyqQ75qjtNGqANMA@mail.gmail.com","subject":"Re: Bulgarian translation of git","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-02-15T18:09:37Z","receivedAt":"2012-02-15T18:09:37Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jiang Xin <worldhello.net@gmail.com> writes:\n\n> I squash the following in the pot initial commit, and update the commit log.\n> commit:  https://github.com/gotgit/git-po/commit/master%5E\n>\n> diff --git a/Makefile b/Makefile\n> index 87fb3..88268 100644\n> --- a/Makefile\n> +++ b/Makefile\n> @@ -2576,7 +2576,6 @@ dist-doc:\n>\n>  distclean: clean\n>         $(RM) configure\n> -       $(RM) po/git.pot\n\nYeah, that change is very sensible.  I am surprised that nobody noticed it\nso far while this topic was discussed.\n"}]}