{"thread":{"id":"29516","subject":"Re: [PATCH] i18n: po for zh_cn","startedAt":"2012-02-02T10:04:50Z","lastAt":"2012-02-02T19:20:29Z","messageCount":2,"participants":["Frederik Schwarzer","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"183571","messageId":"201202021104.50534.schwarzerf@gmail.com","threadId":"29516","inReplyTo":null,"subject":"Re: [PATCH] i18n: po for zh_cn","fromName":"Frederik Schwarzer","fromEmail":"schwarzerf@gmail.com","sentAt":"2012-02-02T10:04:50Z","receivedAt":"2012-02-02T10:04:50Z","isPatch":true,"sender":{"key":"schwarzerf@gmail.com","avatar":null},"body":"Am Donnerstag, 2. Februar 2012, 09:15:38 schrieben Sie:\n\n(damn, my mail programme always answers to the sender only ...)\n\nHi,\n\n> Jiang Xin <worldhello.net@gmail.com> writes:\n> > 2012/2/2 Junio C Hamano <gitster@pobox.com>:\n> > ...\n> > \n> >>  (6) From time to time, the l10n coordinator will pull from\n> >>  \"git.git\" when\n> >>  \n> >>     meaningful number of changes are made to the translatable\n> >>     strings.  I hope this would happen much less often than\n> >>     once per week, preferably much less frequently. The l10n\n> >>     coordinator updates po/git.pot and makes a commit, and\n> >>     notifies the l10n teams.\n> > \n> > notifies the l10n teams using another mailing list maybe.\n> \n> I personally think using the regular git@vger.kernel.org list would\n> be preferrable for this.  People who translate would want to learn\n> the reasoning that led to the final phrasing of the messages to\n> come up with usable translation, and following the main list would\n> be one way to do so. Having to follow two separate list will be an\n> unnecessary burden.\n> \n> But the choice of how to coordinate his or her work with the l10n\n> teams is entirely up to the l10n coordinator.\n\nAs I see it there are two kinds of people doing translations. \nDevelopers who also translate and people who want to translate \nsoftware but are not involved in the development.\n\nTranslations of the former group are in many cases suboptimal. But the \nlatter group will not follow this mailing list. They are not \ninterested in all the details. They live in their room, get a piece of \npaper and translate it. In case something is unclear, they aks. But as \nit is now, it would look something like this:\nTranslators receive 100+ emails per day and are supposed to filter out \nthe one email every 10 days that carries useful information for their \nwork. In practice I guess interested Translators (who are not \ninterested in every code detail) will unsubscribe after a few days and \nthen miss all the fun.\n\nA git-i18n mailing list could coordinate that. It would not be a list \nfor l10n teams to do their internal coordination, but for the i18n \ncoordinator to notify l10n teams about updated POT files (he might \neven merge PO files) and for l10n teams to ask about strings they are \nunsure about. These questions would then be digested by the i18n \ncoordinator and brought to the attention of the developers if needed.\n\nHow does that sound?\n\nRegards\n\nPS: I would have even put all the POT/PO stuff in an extra Git \nrepository. Working with translation is decoupled from development \ncleanly by the msginit/msgmerge process but well, it might not be woth \nthat separation for a single project. :)\n"},{"id":"183635","messageId":"7vfwetvy82.fsf@alter.siamese.dyndns.org","threadId":"29516","inReplyTo":"201202021104.50534.schwarzerf@gmail.com","subject":"Re: [PATCH] i18n: po for zh_cn","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-02-02T19:20:29Z","receivedAt":"2012-02-02T19:20:29Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Frederik Schwarzer <schwarzerf@gmail.com> writes:\n\n> Translations of the former group are in many cases suboptimal. But the \n> latter group will not follow this mailing list.\n\nWell, I would have to caution that translations by people who are not\nfamiliar with Git would also be in many cases suboptimal, too.  Have you\nseen translations of technical books by nontechnical people?\n\n> ... In practice I guess interested Translators (who are not \n> interested in every code detail) will unsubscribe after a few days and \n> then miss all the fun.\n\nEver heard of mail filtering by say Subject: or even From: ? ;)\n\n> A git-i18n mailing list could coordinate that. It would not be a list \n> for l10n teams to do their internal coordination, but for the i18n \n> coordinator to notify l10n teams about updated POT files (he might \n> even merge PO files) and for l10n teams to ask about strings they are \n> unsure about. These questions would then be digested by the i18n \n> coordinator and brought to the attention of the developers if needed.\n>\n> How does that sound?\n\nThat is entirely up to the l10n coordinator. Are you volunteering?\n"}]}