{"thread":{"id":"30677","subject":"Please pull git-l10n updates on master branch","startedAt":"2012-06-01T10:20:35Z","lastAt":"2012-06-01T13:49:21Z","messageCount":5,"participants":["Jiang Xin","Stefano Lattarini","Marco Paolone"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"192646","messageId":"CANYiYbF3sbtKVTZJOTbQ-aOjBKGKFZfq-xQDwyOvR56C7akrLw@mail.gmail.com","threadId":"30677","inReplyTo":null,"subject":"Please pull git-l10n updates on master branch","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2012-06-01T10:20:35Z","receivedAt":"2012-06-01T10:20:35Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"Hi Junio,\n\nAs usual, this pull is for master branch. In this pull, both 'it.po'\nand 'zh_CN.po'\nhave fuzzy translations. One translation in 'zh_CN.po' intends to be fuzzy,\nbecause it is hard to translate right, and I sent a patch for this yesterday.\n\n #: builtin/apply.c:3266\n #, fuzzy, c-format\n msgid \"new mode (%o) of %s does not match old mode (%o)%s%s\"\n msgstr \"%2$s 的新模式（%1$o）和旧模式（%3$o）%4$s%5$s 不匹配\"\n\nFuzzy translations won't be compiled to '.mo' files, for we don't pass\n-f/--use-fuzzy\noption to msgfmt when compile '.po' to '.mo'.\n\nThe following changes since commit 9de96815493b577ae791d5113a3e354142ffbcae:\n\n Merge git://github.com/git-l10n/git-po (2012-05-17 15:35:35 -0700)\n\nare available in the git repository at:\n\n\n https://github.com/git-l10n/git-po/ master\n\nfor you to fetch changes up to 5ae481e0ad61f3cdf0b0f6bc3f57bae23574db16:\n\n l10n: Set nplurals of zh_CN.po from 1 to 2 (2012-06-01 17:43:38 +0800)\n\n----------------------------------------------------------------\nJiang Xin (5):\n l10n: Update git.pot (41 new messages)\n Merge branch 'maint'\n l10n: zh.CN.po: update by msgmerge git.pot\n l10n: zh_CN.po: translate 323 new messages\n l10n: Set nplurals of zh_CN.po from 1 to 2\n\nMarco Paolone (1):\n l10n: New it.po file with 504 translations\n\nPeter Krefting (1):\n Update Swedish translation (728t0f0u)\n\nTran Ngoc Quan (2):\n Init translation for Vietnamese\n First release translation for Vietnamese\n\n po/TEAMS | 8 +\n po/git.pot | 171 +-\n po/it.po | 5144 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n po/sv.po | 536 +++---\n po/vi.po | 5360 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n po/zh_CN.po | 2418 ++++++++++++++++++++++-----\n 6 files changed, 12945 insertions(+), 692 deletions(-)\n create mode 100644 po/it.po\n create mode 100644 po/vi.po\n\n--\nJiang Xin\n"},{"id":"192652","messageId":"4FC8A88D.3080700@gmail.com","threadId":"30677","inReplyTo":"CANYiYbF3sbtKVTZJOTbQ-aOjBKGKFZfq-xQDwyOvR56C7akrLw@mail.gmail.com","subject":"Nits abut the italian translation (was: Re: Please pull git-l10n updates on master branch)","fromName":"Stefano Lattarini","fromEmail":"stefano.lattarini@gmail.com","sentAt":"2012-06-01T11:33:33Z","receivedAt":"2012-06-01T11:33:33Z","isPatch":false,"sender":{"key":"stefano.lattarini@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1429199?v=4"},"body":"On 06/01/2012 12:20 PM, Jiang Xin wrote:\n> Hi Junio,\n> \n> As usual, this pull is for master branch. In this pull, both 'it.po'\n> and 'zh_CN.po'\n> have fuzzy translations. One translation in 'zh_CN.po' intends to be fuzzy,\n> because it is hard to translate right, and I sent a patch for this yesterday.\n>\n> Marco Paolone (1):\n> l10n: New it.po file with 504 translations\n>\nI see few minor issues with the new translations; I hope it's OK if I report\nthem here. Do not consider the following as an exhaustive list, since I've\njust skimmed the it.po file. And sorry for the messy and out-of-order report,\nbut I'm short of time in these days.\n\nRegards,\n Stefano\n\n~~~\n\n #: diff.c:1421\n #, c-format\n msgid \", %d insertion(+)\"\n msgid_plural \", %d insertions(+)\"\n msgstr[0] \", %d aggiunta(+)\"\n msgstr[1] \", %d aggiunte(+)<\"\n\nSpurious \"<\" here?\n\n~~~\n\n #: help.c:214\n msgid \"git commands available from elsewhere on your $PATH\"\n msgstr \"i comandi git sono disponibili in un altro percorso nel tuo $PATH\"\n\nGiven the context this message is use in (output of \"git help -a\"), I think a\nmore correct translation would be:\n\n comandi git disponibili altrove nel tuo $PATH\n\n~~~\n\n #: sequencer.c:403\n #, c-format, fuzzy\n msgid \"Cannot get commit message for %s\"\n msgstr \"Non è possibile prelevare il messaggio di commit per %s\"\n\nWhat about \"Impossibile ottenere il messaggio di commit per %s\" instead?\n\"Prelevare\" sounds weird in this context, at least to me ...\n\n~~~\n\n\"branch\" is sometimes translated, sometimes not:\n\n #: wt-status.c:744\n msgid \"Not currently on any branch.\"\n msgstr \"Al momento non si è su alcun ramo.\"\n\n #: sha1_name.c:869\n #, c-format\n msgid \"No upstream configured for branch '%s'\"\n msgstr \"Nessun upstream configurato per il branch '%s'\"\n\nBTW, are we sure it's a good idea to translate technical terms like\n'branch'? And if yes, why translate some terms (branch -> albero),\nbut not others (tag -> etichetta)?\n\n~~~\n\n #. TRANSLATORS: Make sure to include [Y] and [n] in your\n #. translation. The program will only accept English input\n #. at this point.\n #: git-bisect.sh:279\n msgid \"Are you sure [Y/n]? \"\n msgstr \"Si è sicuri? [S/n] \"\n\nThe translation \"[S/n]\" seems to contradict the comment above.\n\n #. TRANSLATORS: Make sure to include [y], [n], [e], [v] and [a]\n #. in your translation. The program will only accept English\n #. input at this point.\n #: git-am.sh:766\n #, fuzzy\n msgid \"Apply? [y]es/[n]o/[e]dit/[v]iew patch/[a]ccept all \"\n msgstr \"Applicare? [s]ì/[n]o/[m]odifica/[v]isualizza/mostra [p]atch/[a]ccetta tutto \"\n\nLikewise, but worse.\n\n~~~\n\n #: common-cmds.h:28\n #, fuzzy\n msgid \"Create, list, delete or verify a tag object signed with GPG\"\n msgstr \"Crea, elenca. elimina o verifica un oggetto tag firmato con GPG\"\n\nMinor typo: should be \"elenca,\" not \"elenca.\".\n\n~~~\n\n #: builtin/tag.c:376\n #, c-format, fuzzy\n msgid \"The tag message has been left in %s\\n\"\n msgstr \"Il messaggio tag è stato lasciato in %s\\n\"\n\n\"Il messaggio del tag\" or \"Il messaggio associato al tag\" seems clearer and more\ncorrect.\n\n~~~\n\n\n #: builtin/reset.c:325\n #, c-format, fuzzy\n msgid \"%s reset is not allowed in a bare repository\"\n msgstr \"%s reset non è consentito in un archivio scoperto #FIXME: bare\"\n\nWhat about translating \"bare\" with \"spoglio\"?\n\n~~~\n\n #: builtin/mv.c:171\n msgid \"not under version control\"\n msgstr \"non si trova nel sistema di controllo versione\"\n\nWhat about \"non e' sotto controllo di versione\"? It seems a slightly more\nfaithful translation to me.\n\n~~~\n\n #: builtin/merge.c:1146 builtin/merge.c:1303\n #, c-format, fuzzy\n msgid \"%s - not something we can merge\"\n msgstr \"%s - non è qualcosa per cui effettuare il merge\"\n\nI'd say: \"non è qualcosa per cui possiamo effettuare il merge\"\n\n~~~\n\n #: builtin/help.c:108\n #, c-format\n msgid \"emacsclient version '%d' too old (< 22).\"\n msgstr \"la versione '%d' di emacsclient è vecchia (<22).\"\n\ns/vecchia/troppo vecchia/?\n\n~~~\n\n #: builtin/commit.c:1588\n msgid \"\"\n \"Repository has been updated, but unable to write\\n\"\n \"new_index file. Check that disk is not full or quota is\\n\"\n \"not exceeded, and then \\\"git reset HEAD\\\" to recover.\"\n msgstr \"\"\n \"L'archivio è stato aggiornato, ma non è stato possibile scrivere il file\\n\"\n \"new_index. Verificare che l'unità disco non sia piena o che la quota non sia\\n\"\n \"stata superata, ed eseguire \\\"git reset HEAD\\\"ccc per il ripristino.\"\n\nWhat is that \"ccc\" after \"HEAD\" for?\n\n~~~\n\n #: builtin/add.c:297\n msgid \"Empty patch. Aborted.\"\n msgstr \"Patch vuota. Operazione terminata.\"\n\nI beliave \"bloccata\" (or even \"abortita\") would be clearer than \"terminata\" in\nthis context?\n"},{"id":"192657","messageId":"20120601123642.GA11543@quizzlo.invalid","threadId":"30677","inReplyTo":"4FC8A88D.3080700@gmail.com","subject":"Re: Nits abut the italian translation (was: Re: Please pull git-l10n updates on master branch)","fromName":"Marco Paolone","fromEmail":"marcopaolone@gmail.com","sentAt":"2012-06-01T12:36:42Z","receivedAt":"2012-06-01T12:36:42Z","isPatch":false,"sender":{"key":"marcopaolone@gmail.com","avatar":null},"body":"On Fri, Jun 01, 2012 at 01:33:33PM +0200, Stefano Lattarini wrote:\n> I see few minor issues with the new translations; I hope it's OK if I report\n> them here. Do not consider the following as an exhaustive list, since I've\n> just skimmed the it.po file. And sorry for the messy and out-of-order report,\n> but I'm short of time in these days.\n\nThanks for your report, I'll fix them in next commit. We could even leave terms\nlike \"branch\" or \"tree\" untranslated, but translation wouldn't have much sense\nat this point. Some guides, like [1] use \"ramo\" or \"albero\" to better explain\nhow Git works, especially for beginners. Obviously we should leave terms like\n\"cherry-pick\" or \"push\" as is. What do you suggest?\n\n[1] http://www.linux.it/~rubini/docs/git/git.html\n\n-- \nLinux Registered User #401479\nGPG: 0x897AF14E\n"},{"id":"192659","messageId":"4FC8C434.1050902@gmail.com","threadId":"30677","inReplyTo":"20120601123642.GA11543@quizzlo.invalid","subject":"Re: Nits abut the italian translation","fromName":"Stefano Lattarini","fromEmail":"stefano.lattarini@gmail.com","sentAt":"2012-06-01T13:31:32Z","receivedAt":"2012-06-01T13:31:32Z","isPatch":false,"sender":{"key":"stefano.lattarini@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1429199?v=4"},"body":"On 06/01/2012 02:36 PM, Marco Paolone wrote:\n> On Fri, Jun 01, 2012 at 01:33:33PM +0200, Stefano Lattarini wrote:\n>> I see few minor issues with the new translations; I hope it's OK if I report\n>> them here. Do not consider the following as an exhaustive list, since I've\n>> just skimmed the it.po file. And sorry for the messy and out-of-order report,\n>> but I'm short of time in these days.\n> \n> Thanks for your report, I'll fix them in next commit.\n>\nThanks.\n\n> We could even leave terms like \"branch\" or \"tree\" untranslated, but translation\n> wouldn't have much sense at this point. Some guides, like [1] use \"ramo\" or\n> \"albero\" to better explain how Git works, especially for beginners. Obviously\n> we should leave terms like \"cherry-pick\" or \"push\" as is. What do you suggest?\n>\nI have no strong feeling honestly (as I'm no user of localized messages myself);\nwhat I suggest is that you should decide to either translate all the \"translatable\"\ntechnical terms (e.g., if you go for \"branch -> ramo\" and \"tree -> albero\", you\nmust also go for \"tag -> etichetta\"), or none of them (that is my personal opinion\nthough, and other people might legitimately disagree). In the former case, adding\na new help category (say \"translation\") that explains how the terms and concepts\nare mapped from the original english to the current language might be a good idea:\n\n $ git help translation\n Git parla italiano ora!\n [ ... blah blah ... piu' dettagli qui ...]\n branch -> ramo\n tag -> etichetta\n directory -> cartella\n ...\n\nRegards,\n Stefano\n"},{"id":"192660","messageId":"CANYiYbGgPZMYC9ea8jsKkz6ybBBb_Kyx+gBFncaGYW=Wh0m-Zg@mail.gmail.com","threadId":"30677","inReplyTo":"20120601123642.GA11543@quizzlo.invalid","subject":"Re: Nits abut the italian translation (was: Re: Please pull git-l10n updates on master branch)","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2012-06-01T13:49:21Z","receivedAt":"2012-06-01T13:49:21Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2012/6/1 Marco Paolone :\n> Thanks for your report, I'll fix them in next commit.  We could even leave terms\n\nItalian team may have team members this time, update the po/TEAMS\nfile, and when there are new translation updates, you can send\nreview request to other team members.\n\nDifferent l10n teams have different ways for communication.\nThe German l10n team uses this list, while Chinese l10n team\nuse weibo (a twitter clone, because of the strict Internet censorship\nin China) and googlegroup, such as http://groups.google.com/group/gotgit.\n\n-- \nJiang Xin\n"}]}