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 <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 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
Received on Wed Aug 4 18:46:22 2004