| 1 | = Transifex = |
| 2 | BOINC's localization efforts are focused around the Transifex localization platform. You can find |
| 3 | it [https://www.transifex.com/projects/p/boinc/ here]. |
| 4 | |
| 5 | Central to the smooth use of this platform is the TransifexGithub bridge. |
| 6 | |
| 7 | txgh handles the following job functions: |
| 8 | * Updates Transifex's copy of the templates when a updated localization template is committed. |
| 9 | * Commits completed localizations back to Github. |
| 10 | |
| 11 | From a developer perspective they only need to commit updated localization templates for all the localizers to be |
| 12 | notified of the changes. When localizations have been completed the updated localization files will automatically |
| 13 | be committed for use by the community. |
| 14 | |
| 15 | '''NOTE:''' At present, BOINC's server is considered the authoritative source for the git repository. If txgh has |
| 16 | successfully committed completed localizations to Github and someone commits to BOINC's git repo the changes will |
| 17 | be lost. Periodically, the person in charge of monitoring the localization system needs to pull down the localization |
| 18 | updates and push them to the git repo on the BOINC server. |
| 19 | |
| 20 | == Transifex Workflow == |
| 21 | |
| 22 | Here is some documentation on using Transifex: |
| 23 | [http://docs.transifex.com/tutorials/content] |
| 24 | |
| 25 | == !TransifexGithub Bridge == |
| 26 | |
| 27 | Instructions for setting up a new bridge server can be found here: |
| 28 | [https://github.com/BOINC/txgh] |
| 29 | |
| 30 | Additional documentation from Transifex: |
| 31 | [http://docs.transifex.com/integrations/github] |
| 32 | |
| 33 | The Transifex configuration file is stored in the BOINC source repo at: |
| 34 | boinc/locale/txconfig |
| 35 | |
| 36 | |
| 37 | |
| 38 | |