[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Q] Including new translations

From: Kobayashi Noritada <nori1_at_dolphin.c.u-tokyo.ac.jp>
Date: 2004-08-04 13:09:19 CEST


From: "Peter N. Lundblad" <peter@famlundblad.se>
Subject: Re: [Q] Including new translations
Date: Thu, 29 Jul 2004 21:08:08 +0200 (CEST)

> > So, as far as the new translations is concerned: We'll need to work out if
> > and how adding them to releases works for the Subversion community. This
> > thread is a nice start for discussing that subject.
> >
> > To give my own opinion:
> > I understand that the Apache community requires 2 translators for every
> > language they add. Not all of our translations pass this requirement, yet I
> > think it is a rule like it would be good.
> >
> > As for the current pt_BR.po and ja.po translations (neither of which has two
> > involved translators), I think that it would be a good idea that they be
> > reviewed by users@ or dev@ list readers before they are merged into the
> > release branch. As things currently stand, there would be enough time to
> > organise this effort before the final release (maybe even before RC2).
> >
> +1. We can add them if they get some review. We can technically validate
> them so they don't introduce bugs.

So far, no one reviewed and sent comments for ja.po to this list.
OTOH some people in Subversion-jp list members <subversion-jp@m.bluegate.org>
looked over the file and gave me some comments.
( Japanese list archives: http://arch.bluegate.org/pipermail/subversion-jp/ )
Reflecting those comments, I modified ja.po considerably at r10468.
Should I ask those people to give comments on this list,
or recruit those who can review and modify ja.po in the repository?

I have another question.
ja.po is a new file created after the branching branches/1.1.x.
Of course it innately contains some new messages added in the trunk tree,
which are not contained in the release branch.
So, if I am allowed to merge ja.po into branches/1.1.x,
I want not to copy it to the release branch directly,
but to make the file conform to the source code of branches/1.1.x
with running 'make locale-gnu-po-update' before adding to the release branch.
Is this operation allowed?


|:  Noritada KOBAYASHI
|:  Dept. of General Systems Studies,
|:  Graduate School of Arts and Sciences, Univ. of Tokyo
|:  E-mail: nori1@dolphin.c.u-tokyo.ac.jp (preferable)
|:          nori@esa.c.u-tokyo.ac.jp
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 4 13:09:45 2004

This is an archived mail posted to the Subversion Dev mailing list.