{"thread":{"id":"30366","subject":"Glossary for bootstrapping Git translations","startedAt":"2012-04-30T10:44:28Z","lastAt":"2012-04-30T15:47:11Z","messageCount":5,"participants":["Ævar Arnfjörð Bjarmason","Nguyen Thai Ngoc Duy","Jiang Xin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"190289","messageId":"CACBZZX7H8qB05qc+ovaeFJ_qR3bF7=uWq6bjOHq8+_YNDLTu2g@mail.gmail.com","threadId":"30366","inReplyTo":null,"subject":"Glossary for bootstrapping Git translations","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2012-04-30T10:44:28Z","receivedAt":"2012-04-30T10:44:28Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Over the weekend I started the Icelandic translation of Git beyond the\ncurrent test messages that are there in po/is.po already.\n\nI find that the most difficult part of getting started is getting all\nthe core terminology of Git straight, i.e. gathering and classifying\nall the jargon involved and translating that. Once that's done the\nrest of the translation is relatively straightforward.\n\nSo with a lot of help from others I've started a glossary for English\n-> Icelandic Git terms hosted at:\n\n    https://raw.github.com/avar/git/avar/is-po/po/is.README\n\nI think having something like this in po/GLOSSARY or in a similar\nlocation would be very useful to get new translators started. I'm\nCC-ing the other translation leads so they can look the English core\nterms I've come up with over, and suggest new ones.\n\nIf we can get together a good glossary then a new translation of Git\nwould be pretty much:\n\n 1. Create a new $lang.po file\n 2. Copy GLOSSARY over to $lang.GLOSSARY\n 3. Try to translate all the core terms\n 4. Once you've got that straight translate the rest of $lang.po\n"},{"id":"190292","messageId":"CACsJy8C6QLYz1fks=r7KbvS80x=x7ZpzfE3ACGOv1S3YEPH4qw@mail.gmail.com","threadId":"30366","inReplyTo":"CACBZZX7H8qB05qc+ovaeFJ_qR3bF7=uWq6bjOHq8+_YNDLTu2g@mail.gmail.com","subject":"Re: Glossary for bootstrapping Git translations","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2012-04-30T11:29:30Z","receivedAt":"2012-04-30T11:29:30Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"2012/4/30 Ævar Arnfjörð Bjarmason <avarab@gmail.com>:\n> I think having something like this in po/GLOSSARY or in a similar\n> location would be very useful to get new translators started. I'm\n> CC-ing the other translation leads so they can look the English core\n> terms I've come up with over, and suggest new ones.\n\nJust checking. Have you looked at Documentation/glossary-content.txt?\nThat and this glossary may not be exactly the same, but you should be\nable to copy some terms from there (e.g. pathspec), or even add some\nback.\n-- \nDuy\n"},{"id":"190297","messageId":"CANYiYbH7g5JRvEQ_b9sEP72zR+yrAj+cQbemi_nsFTSa+QRgEw@mail.gmail.com","threadId":"30366","inReplyTo":"CACBZZX7H8qB05qc+ovaeFJ_qR3bF7=uWq6bjOHq8+_YNDLTu2g@mail.gmail.com","subject":"Re: Glossary for bootstrapping Git translations","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2012-04-30T13:17:34Z","receivedAt":"2012-04-30T13:17:34Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2012/4/30 Ævar Arnfjörð Bjarmason <avarab@gmail.com>:\n> Over the weekend I started the Icelandic translation of Git beyond the\n> current test messages that are there in po/is.po already.\n\nI just created new branch 'maint' in git-po repository on GitHub,\nand generated two different 'git.pot' files yesterday. The\nrecommended workflow for a new language:\n\n1. After fork the git-l10n/git-po on GitHub, checkout the 'maint'\n    branch, or create a new tracking branch based on it.\n\n2. Create your initial XX.po file, tranlate, commit, and push to\n    your own fork.\n\n3. Send a GitHub pull request to the 'maint' branch of git-l10n/git-po.\n\n4. The l10n coordinator merge your commit to the 'maint' branch,\n    so your translation may appear in git next maintainence version,\n    i. e. 1.7.10.1.\n\n5. The l10n coordinator will do a second merge, so new commit in\n    'maint' branch will merge back to the 'master' branch.\n\n6. Update your XX.po in 'master' branch, translate, commit, and\n     send new pull request.\n\n7. The l10n coordinator will merge your updates to 'master' branch,\n     and your translations will come with git 1.7.11.\n\nL10N team leaders may already noticed these changes, as I @ all\nteam leaders in the commit comments.\n\n* https://github.com/git-l10n/git-po/commit/cd1e74874049c8ba8e510f2fae064e510cccd32b#commitcomment-1271645\n* https://github.com/git-l10n/git-po/commit/df3ef6fb98a276fa62bbcf129d40307b00253588#commitcomment-1271639\n\n--\nJiang Xin\n"},{"id":"190298","messageId":"CACBZZX57-=fM+wVrFhooBB4wrbUBT1WXdb5NYXK6Lv=zEMLNKQ@mail.gmail.com","threadId":"30366","inReplyTo":"CACsJy8C6QLYz1fks=r7KbvS80x=x7ZpzfE3ACGOv1S3YEPH4qw@mail.gmail.com","subject":"Re: Glossary for bootstrapping Git translations","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2012-04-30T14:20:48Z","receivedAt":"2012-04-30T14:20:48Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Mon, Apr 30, 2012 at 13:29, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:\n> 2012/4/30 Ævar Arnfjörð Bjarmason <avarab@gmail.com>:\n>> I think having something like this in po/GLOSSARY or in a similar\n>> location would be very useful to get new translators started. I'm\n>> CC-ing the other translation leads so they can look the English core\n>> terms I've come up with over, and suggest new ones.\n>\n> Just checking. Have you looked at Documentation/glossary-content.txt?\n> That and this glossary may not be exactly the same, but you should be\n> able to copy some terms from there (e.g. pathspec), or even add some\n> back.\n\nI hadn't seen it recently. I think I'll incorporate some things from it.\n\nIn practice translators don't have to worry about many of those terms,\nso I think there's some value in having another document for terms\nthey need to get straight to get a translation started.\n"},{"id":"190310","messageId":"CACBZZX4cBO7QJ7JHTpiw0E61pb=Z176cVkjteY=qb+PGBr=jsg@mail.gmail.com","threadId":"30366","inReplyTo":"CANYiYbH7g5JRvEQ_b9sEP72zR+yrAj+cQbemi_nsFTSa+QRgEw@mail.gmail.com","subject":"Re: Glossary for bootstrapping Git translations","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2012-04-30T15:47:11Z","receivedAt":"2012-04-30T15:47:11Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Mon, Apr 30, 2012 at 15:17, Jiang Xin <worldhello.net@gmail.com> wrote:\n> 2012/4/30 Ævar Arnfjörð Bjarmason <avarab@gmail.com>:\n>> Over the weekend I started the Icelandic translation of Git beyond the\n>> current test messages that are there in po/is.po already.\n>\n> I just created new branch 'maint' in git-po repository on GitHub,\n> and generated two different 'git.pot' files yesterday. The\n> recommended workflow for a new language:\n>\n> 1. After fork the git-l10n/git-po on GitHub, checkout the 'maint'\n>    branch, or create a new tracking branch based on it.\n>\n> 2. Create your initial XX.po file, tranlate, commit, and push to\n>    your own fork.\n>\n> 3. Send a GitHub pull request to the 'maint' branch of git-l10n/git-po.\n>\n> 4. The l10n coordinator merge your commit to the 'maint' branch,\n>    so your translation may appear in git next maintainence version,\n>    i. e. 1.7.10.1.\n>\n> 5. The l10n coordinator will do a second merge, so new commit in\n>    'maint' branch will merge back to the 'master' branch.\n>\n> 6. Update your XX.po in 'master' branch, translate, commit, and\n>     send new pull request.\n>\n> 7. The l10n coordinator will merge your updates to 'master' branch,\n>     and your translations will come with git 1.7.11.\n>\n> L10N team leaders may already noticed these changes, as I @ all\n> team leaders in the commit comments.\n\nThanks for the workflow advice. I'll be funneling translations though\nyou once I'm happy enough with is.po. For now I'm still mulling over\nhow to translate a few remaining things.\n"}]}