Stefan Kueng wrote on Sat, Feb 04, 2017 at 17:13:06 +0100:
> 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.
ASF has a Pootle instance: https://translate.apache.org/
> 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?
I'd certainly be willing to consider changes to make people's workflows
easier, but what reason do we have to project that changing the workflow
will result in more translation work getting done? No existing or
prospective translator has asked dev@ to change our workflow.
(To clarify, I'm not objecting; simply seeking clarification.)
For reference, the process today is:
.
svn co https://svn.apache.org/repos/asf/subversion/trunk svn-trunk
cd svn-trunk
tools/po/po-update.sh
<edit>
<send a patch>
> I'm bringing this up again since I noticed that the existing translations
> are very old and outdated. And since TSVN is fully translated in many
> languages, the new conflict resolver UI would still show the English strings
> since they now come from the svn lib.
Well, of course more translations would be a good thing. Perhaps some
of the TSVN translators could translate Subversion itself as well? It
would be great if they could join this thread.
Cheers,
Daniel
Received on 2017-02-04 18:20:46 CET