Re: [Q] Including new translations

[Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp>]

Hi,

From: "Peter N. Lundblad" <pe...@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 <su...@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?

Thanks,

-- 
|:  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

Re: [Q] Including new translations

[Ben Reser <be...@reser.org>]

On Wed, Aug 04, 2004 at 07:10:35PM +0200, Peter N. Lundblad wrote:
> As I said before, I don't see why he needs to remove unused messages.
> Still I interpret this as doing make locale-gnu-po-update after merging,
> then just checking in is OK. That's good, since it produces clenaer .po
> files in the release.

Ohh I don't think it's a big deal.  Just think it'd be nice if we kept
things cleaner.

-- 
Ben Reser <be...@reser.org>
http://ben.reser.org

"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [Q] Including new translations

["Peter N. Lundblad" <pe...@famlundblad.se>]

On Wed, 4 Aug 2004, Ben Reser wrote:

> On Wed, Aug 04, 2004 at 08:09:19PM +0900, Kobayashi Noritada wrote:
> > 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?
>
> You'd need to remove these extra messages.  But you can merge and then
> edit it.
>
As I said before, I don't see why he needs to remove unused messages.
Still I interpret this as doing make locale-gnu-po-update after merging,
then just checking in is OK. That's good, since it produces clenaer .po
files in the release.

Regards,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [Q] Including new translations

[Ben Reser <be...@reser.org>]

On Wed, Aug 04, 2004 at 08:09:19PM +0900, Kobayashi Noritada wrote:
> 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?

You'd need to remove these extra messages.  But you can merge and then
edit it.

-- 
Ben Reser <be...@reser.org>
http://ben.reser.org

"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [Q] Including new translations

["Peter N. Lundblad" <pe...@famlundblad.se>]

On Wed, 4 Aug 2004, Kobayashi Noritada wrote:

> So far, no one reviewed and sent comments for ja.po to this list.
> OTOH some people in Subversion-jp list members <su...@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 would say that the important thing is to have a review, not that it is
on this list. svn-jp seems more appropriate, since many of the members of
dev@subversion won't understand what you're talking about anyway:-) We
usually give reviewers credit in the log messages, though. If you do this,
we will know that there was review. This is one reason I don't like the
two-translators required proposal that was made here some week ago. If you
get reviews from non-developers and there is one translator that's enough
IMO.

> 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?
>
Not sure, actually. IMO, I don't think it's a problem if you get some
unused messages from trunk. An update is more than a merge and I don't
know how we handle this in other cases if there are any.

My 2 cents,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org