Stefan K, trying to help push this forward...
We have consensus to do something about automatically providing updates
to translatable strings. We need some help to fill in the details and
actually do it.
From my perspective, it looks like we should:
* Instantiate a bot (buildbot) that will...
- do we have a volunteer?
* Check out the trunk (and any configured branches).
* Run 'make po-update'.
* (?) Upload the updated 'subversion.pot' and/or '*.po' files
to services including Pootle and Transifex.
- how exactly should it upload to Pootle?
- how exactly should it upload to Transifex?
* (?) Commit the updated 'subversion.pot' and/or '*.po' files.
- which files? when (see below)?
* Activate a Transifex.com account for Subversion.
- how? can you do it?
Re committing: I think we should rate-limit these commits to once per
day, and should not commit when there are no real changes to the
translatable strings but only changes in the source line number
An alternative to committing would be to upload these files to some
place where translators can fetch them. Somewhere on apache.org and/or
if the Pootle and/or Transifex services make these files easily
available then that's fine, we can point at those, no need to commit.
- Do they? What are the URLs?
Can you and others help fill in the details?
On 04/02/17, Stefan Kueng wrote:
> I remember there was a discussion about two years ago about using a web
> based translation tool for Subversion (e.g.
> http://translationproject.org/), but that discussion got to no real
> For TSVN we use transifex (https://www.transifex.com/) which is free for
> open source projects. Works quite well - it updates the new strings
> automatically from our repository pot file.
> Even if Subversion does not move to use such a web based tool: how about
> providing the source pot file in the repository which should be updated
> frequently so translators can use that file without having to install
> and parse the whole svn source?
Received on 2017-03-13 11:52:56 CET