Thomas,
Our code base has moved to GitHub. I have a translation branch there
called 'translations': https://github.com/audacity/audacity/network
If you would like to set up Transifex integration to commit po files
to *your* fork of Audacity repo on GitHub, then I can easily pick
them up from there. It is easy and free to set up an account at
GitHub and fork the Audacity repo. Presumably Transifex integration
will take care of the rest? If the updated .po files are in your
copy, I can then collect them easily, collecting multiple languages
in one step. That would indeed make things a lot easier for me.
I suggest this way, as I do not want translations to go
automatically from Transifex in to the main Audacity repo. For
example I want to screen for typos on %s which will cause crashes.
Would making me a manager of the Audacity Transifex group you have
set up help make the flow from Transifex to Audacity easier?
Transifex integration doesn't stop us taking translations by other
routes. Translations by sending to this audacity-translation list will
continue to be welcome.
--James.
On 28/04/2015 12:01, Thomas De Rocker wrote:
And to answer your other question: when I look at the timeline of
Transifex, i see recent commits to languagesBulgarian
* Russian
* Polish
* German
* Portuguese
In my opinion, it would take a lot of work off the shoulders of the
developers who have to commit translations manually right now... It's
been discussed before.
Regards
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Audacity-translation mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-translation
