In order to translate the language files, translators currently have to: 1. use git to clone the repository 2. run the locale/update_po_files.sh script 3. edit the translation file with an offline tool like POEdit 4. create a pull request
This requires a lot of knowledge. An alternative could be to simply download the language file from github, translate it with an offline tool, and send it to this mailing list, so that someone can take care of it. This requires that the .po files are up-to-date, and a manual operation by the maintainers. What about automating the translation process? Here's what I'm thinking about: 1. when someone/something pushes to the master branch, a TravisCI job run the locale/update_po_files.sh script and, if needed, pushes to the master branch itself the updated audacity.pot file (and only it) 2. we can configure a crowdin.com project (it's free for open source projects), which integrates automatically with github repositories So, translators have just to translate files on crowdin.com, and maintainers doesn't have to do anything except setting up the crowdin project... -- Michele _______________________________________________ Audacity-translation mailing list Audacity-translation@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/audacity-translation
