Re: [PATCH] i18n: po for zh_cn

From: Frederik Schwarzer <schwarzerf@gmail.com>
Date: Feb 2, 2012, 10:04 UTC
Message-ID: <201202021104.50534.schwarzerf@gmail.com>

Am Donnerstag, 2. Februar 2012, 09:15:38 schrieben Sie:

(damn, my mail programme always answers to the sender only ...)

Hi,

Show 24 quoted lines

> Jiang Xin <worldhello.net@gmail.com> writes:
> > 2012/2/2 Junio C Hamano <gitster@pobox.com>:
> > ...
> > 
> >>  (6) From time to time, the l10n coordinator will pull from
> >>  "git.git" when
> >>  
> >>     meaningful number of changes are made to the translatable
> >>     strings.  I hope this would happen much less often than
> >>     once per week, preferably much less frequently. The l10n
> >>     coordinator updates po/git.pot and makes a commit, and
> >>     notifies the l10n teams.
> > 
> > notifies the l10n teams using another mailing list maybe.
> 
> I personally think using the regular git@vger.kernel.org list would
> be preferrable for this.  People who translate would want to learn
> the reasoning that led to the final phrasing of the messages to
> come up with usable translation, and following the main list would
> be one way to do so. Having to follow two separate list will be an
> unnecessary burden.
> 
> But the choice of how to coordinate his or her work with the l10n
> teams is entirely up to the l10n coordinator.

As I see it there are two kinds of people doing translations. Developers who also translate and people who want to translate software but are not involved in the development.

Translations of the former group are in many cases suboptimal. But the latter group will not follow this mailing list. They are not interested in all the details. They live in their room, get a piece of paper and translate it. In case something is unclear, they aks. But as it is now, it would look something like this: Translators receive 100+ emails per day and are supposed to filter out the one email every 10 days that carries useful information for their work. In practice I guess interested Translators (who are not interested in every code detail) will unsubscribe after a few days and then miss all the fun.

A git-i18n mailing list could coordinate that. It would not be a list for l10n teams to do their internal coordination, but for the i18n coordinator to notify l10n teams about updated POT files (he might even merge PO files) and for l10n teams to ask about strings they are unsure about. These questions would then be digested by the i18n coordinator and brought to the attention of the developers if needed.

How does that sound?

Regards

PS: I would have even put all the POT/PO stuff in an extra Git 
repository. Working with translation is decoupled from development 
cleanly by the msginit/msgmerge process but well, it might not be woth 
that separation for a single project. :)