[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: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2004-07-29 17:26:04 CEST

Hi Kobayashi,

> I have a question about po-related work.
> It may be related to another thread "svn commit: r10429 -
> branches/1.1.x/subversion/po".
> After branching 'branches/1.1.x", ja.po was added to the directory
> 'trunk/subversion/po', and pt_BR.po will also be soon.
> In the aspect of stabilizing, these two new po files may not be
> added to this branch.
> But these po files will be welcome by those who use ja or pt_BR, and
> another branching for a new release (1.2.x?) will be far away.
> So, I wish to have these po files added to the branched po directory.
> Is it allowed to add these files to 'branches/1.1.x/subversion/po'?

> As a maintainer for ja.po, I am ready to make sure that all the
> translated message is valid for the branched source code, if required.

I understand that you want to make sure that your recent work becomes
available instead of sit around unused in our repository for months. So let
me reassure you that merging rules do not prohibit the ja.po from being
merged to the release branch. This means that - if the correct procedure is
used - ja.po (and other translations) can be added to the release branch
even though that it was not available at branch creation time.

The thread you quoted is currently discussing whether I was allowed to merge
the changes in the other translations to the release branch *without
organising a vote* on the changes first. Some have expressed that they
interpreted the rules that I was allowed to do it, while Peter Lundblad (who
proposed these rules) meant to have written them *not* to allow me to do it.

If I had followed the strictest procedure we have for merge requests, there
would not have been a discussion in that thread.

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).



NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 29 17:26:14 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.