Re: translations (buildbot to update translatable strings)

[Julian Foad <ju...@apache.org>]

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 
reference comments.

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?

- Julian


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
> decision.
> 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?
> [...]

RE: translations (buildbot to update translatable strings)

[Bert Huijben <be...@qqmail.nl>]

> -----Original Message-----
> From: Julian Foad [mailto:julianfoad@apache.org]
> Sent: maandag 13 maart 2017 11:53
> To: Stefan Kueng <to...@gmail.com>
> Cc: Subversion Development <de...@subversion.apache.org>
> Subject: Re: translations (buildbot to update translatable strings)
> 
> 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'.

If nobody else steps up, I can handle this part.

>    * (?) 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?

Also willing to work on this part, after we have that info.

>    * (?) 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
> reference comments.
> 
> 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?

I would start with this second scheme... Perhaps even add an option to one of our scripts to fetch the latest version at [build/invoke], for easy testing and committing around releases.

Not sure if we should really start auto commits on our tree...

Don't see a good use for these auto commits on trunk, as that code is seldom used in production... 
And I would like to be careful with our release branches, on not creating too many unneeded commits that could be collapsed...

	Bert

Re: translations (buildbot to update translatable strings)

[Stefan Kueng <to...@gmail.com>]

On 13.03.2017 11:52, Julian Foad wrote:
> 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?

I don't know about pootle, but Transifex fetches the files itself from a 
specified url or urls.
In TSVN, we have the pot file in the repository, and Transifex just 
fetches it from there. Not sure about the interval it fetches the files, 
but it is fine for TSVN.

>
>   * (?) Commit the updated 'subversion.pot' and/or '*.po' files.
>     - which files? when (see below)?

Transifex provides a script which can be run to update the translated po 
files from their servers and apply the changes to the local files.
In TSVN we have the translated po files also in the repository so the 
build script (which also builds the installers for the different 
languages) has everything ready.

> * Activate a Transifex.com account for Subversion.
>   - how? can you do it?

I suggest that more than just one svn dev signs up there - just one is 
dangerous in case of a bus-factor situation.

>
> 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
> reference comments.

Again, talking about TSVN: we run the transifex script to fetch the 
translated po files once a week. For us that's enough.

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

Transifex allows to download and upload the po files easily. For TSVN 
German, the urls are:
https://www.transifex.com/luebbe/tortoisesvn/trunk-gui/de/download/for_translation/
for the whole po file ready for translation, and there are even urls to 
download a po file with only the translated strings in them.


Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net