You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Mattias Engdegård <ma...@bredband.net> on 2014/02/22 13:57:36 UTC
Re: localisation: status, migration to pootle
Sorry about resuming an old thread, but since most translations are
not kept up to date, what about switching to the Translation Project
instead?
There are experienced teams for the languages that Subversion is
currently translated into and many more. The risk for orphaned
localisations will be lower since the teams deal with continuity
themselves. Users will enjoy higher consistency in terms of vocabulary
and style across software packages.
The details can be read at http://translationproject.org, but in
essence, it would work as follows:
1. As a release is getting near, the Subversion release manager sends
the .pot file, or an URL to a source tarball containing the .pot file
(that is up to date), to the project.
2. As each translation is finished, a robot will send the .po file to
this list.
3. Someone, perhaps the release manager, commits the .po files as they
arrive.
Re: localisation: status, migration to pootle
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Daniel Shahaf wrote on Sun, Mar 09, 2014 at 15:31:14 +0000:
> The requirements ASF poses are ICLA §5 plus a policy that patches are
> not merged if their author doesn't want them to be (regardless of license).
To save everyone looking that up: it's the clause that says you will
only commit stuff that you are legally allowed to commit (e.g.,
copyright-wise).
https://www.apache.org/licenses/icla.txt
Re: localisation: status, migration to pootle
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Mattias Engdegård wrote on Sun, Mar 09, 2014 at 15:48:27 +0100:
> 22 feb 2014 kl. 13.57 skrev Mattias Engdegård:
>
> >Sorry about resuming an old thread, but since most translations
> >are not kept up to date, what about switching to the Translation
> >Project instead?
>
> Given the lack of response, the conclusion is that there is no
> interest for such a migration, but no firm resistance either. In an
> attempt to sweeten the deal, I'll take care of the initial legwork
> myself, priming the pump and propose documentation patches as
> necessary.
>
Note the legal/policy part of accepting contributions of third parties.
The requirements ASF poses are ICLA §5 plus a policy that patches are
not merged if their author doesn't want them to be (regardless of license).
I looked up TP's policy a a few weeks ago and I don't think accepting
patches from TP will be a problem.
#include <disclaimers/IANAL.h>
Daniel
> The plan would be to start with the most recent release, 1.8.8, and
> to have the translation machinery well-oiled in time for 1.9.0. What
> about it?
>
Re: localisation: status, migration to pootle
Posted by Julian Foad <ju...@btopenworld.com>.
Branko Čibej wrote:
> On 09.03.2014 15:48, Mattias Engdegård wrote:
>> 22 feb 2014 kl. 13.57 skrev Mattias Engdegård:
>>> Sorry about resuming an old thread, but since most translations are not
>>> kept up to date, what about switching to the Translation Project instead?
>>
>> Given the lack of response, the conclusion is that there is no
>> interest for such a migration, but no firm resistance either. In
It sounds like a good idea to me, but I'm not a translator. There *are* some existing translators of Subversion, but maybe they are not reading the dev list, or haven't noticed your email. (I suppose it's been a long time since we last gave then anything substantially new to translate.)
I think it would be polite it you attempt to contact them more directly. Aren't there some dedicated mailing lists for Subversion translators? I looked for info on http://subversion.apache.org/docs/community-guide/l10n.html -- which mentions "Translation discussion takes place both on that list
and on dedicated native language mailing lists (l10n-??@subversion.tigris.org)", and on http://subversion.apache.org/mailing-lists.html which has a link right at the end to http://subversion.tigris.org/ds/viewForums.do where there are three listed which don't appear to be recently active (the 'last post date' listed there seems to be wrong -- maybe includes spam?), but maybe some people on those lists are still contactable and interested.
Note also that there is already a Pootle instance for Subversion at <https://translate.apache.org/projects/Subversion/>, with only the German language using it. I have no idea whether that's more or less Good than the Translation Project or if it's a complementary resource.
>> an attempt to sweeten the deal, I'll take care of the initial
>> legwork myself, priming the pump and propose documentation patches
>> as necessary.
It sounds like a good idea for you to set something up so that it's ready to be used, but I'm just concerned that we don't upset anybody by appearing to take away their existing role or work flow from anyone who feels they are the current translator, without consulting them first. Maybe you could set up your own language on TP, and write the instructions for other people to migrate theirs, but don't actually "push the button" for those other languages until you're sure we've made every effort to contact the current volunteers.
What do you think?
- Julian
>> The plan would be to start with the most recent release, 1.8.8,
>> and to have the translation machinery well-oiled in time for
>> 1.9.0. What about it?
>
> I agree. You can't expect developers to define localization
> procedures; it's better to leave that task to translators, who
> actually know what it's all about.
Re: localisation: status, migration to pootle
Posted by Branko Čibej <br...@wandisco.com>.
On 09.03.2014 15:48, Mattias Engdegård wrote:
> 22 feb 2014 kl. 13.57 skrev Mattias Engdegård:
>
>> Sorry about resuming an old thread, but since most translations are
>> not kept up to date, what about switching to the Translation Project
>> instead?
>
> Given the lack of response, the conclusion is that there is no
> interest for such a migration, but no firm resistance either. In an
> attempt to sweeten the deal, I'll take care of the initial legwork
> myself, priming the pump and propose documentation patches as necessary.
>
> The plan would be to start with the most recent release, 1.8.8, and to
> have the translation machinery well-oiled in time for 1.9.0. What
> about it?
I agree. You can't expect developers to define localization procedures;
it's better to leave that task to translators, who actually know what
it's all about.
-- Brane
--
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com
Re: localisation: status, migration to pootle
Posted by Mattias Engdegård <ma...@bredband.net>.
22 feb 2014 kl. 13.57 skrev Mattias Engdegård:
> Sorry about resuming an old thread, but since most translations are
> not kept up to date, what about switching to the Translation Project
> instead?
Given the lack of response, the conclusion is that there is no
interest for such a migration, but no firm resistance either. In an
attempt to sweeten the deal, I'll take care of the initial legwork
myself, priming the pump and propose documentation patches as necessary.
The plan would be to start with the most recent release, 1.8.8, and to
have the translation machinery well-oiled in time for 1.9.0. What
about it?