= Transifex =

THE FOLLOWING IS DEPRECATED.
CHRISTIAN IS DOING IT A DIFFERENT WAY (PLEASE DOCUMENT).

Workflow is:
build translation templates in release branch.
Check them into master.

When make a release branch, make the templates.
All subsequent translation is for the new branch.
------------------------------
BOINC's localization efforts are focused around the Transifex localization platform.  You can find 
it [https://www.transifex.com/projects/p/boinc/ here].

Central to the smooth use of this platform is the !TransifexGithub bridge.

txgh handles the following job functions:
* Updates Transifex's copy of the templates when a updated localization template is committed.
* Commits completed localizations back to Github.

From a developer perspective they only need to commit updated localization templates for all the localizers to be 
notified of the changes.  When localizations have been completed the updated localization files will automatically 
be committed for use by the community.

'''NOTE:''' At present, the Transifex platform is considered the authoritative source for localization. If someone commits changes to localizations directly into the BOINC github repository (e.g. via a Pull Request) they will get overwritten by txgh when someone changes a translation on Transifex.

== Transifex Workflow ==

Here is some documentation on using Transifex:
[http://docs.transifex.com/tutorials/content]

== !TransifexGithub Bridge ==

Instructions for setting up a new bridge server can be found here:
[https://github.com/BOINC/txgh]

Additional documentation from Transifex:
[http://docs.transifex.com/integrations/github]

The Transifex configuration file is stored in the BOINC source repo at:
boinc/locale/txconfig