| 70 | | The easiest way is to use the |
| 71 | | [TranslateIntro BOINC Translation Service], |
| 72 | | a web-based system that's used for BOINC itself and for SETI@home. |
| 73 | | To do this: |
| 74 | | |
| 75 | | * Create a directory, within your revision control system, called '''locale''', with a subdirectory for each language and a templates. This repository must be accessable by a user '''boincadm'''. |
| 76 | | * Post a request to the [http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_loc boinc_loc@ssl.berkeley.edu] email list, asking that your project be added to the BOINC Translation Service. |
| 77 | | |
| 78 | | When this is set up, translations will automatically be checked into your locale/ repository. |
| 79 | | You'll need to periodically update the working copy of this on your web server. |
| 80 | | You'll also need to move translation files from, e.g., '''locale/es/web.po''' to '''project_root/html/project/project_specific_translations/es.po'''. |
| 81 | | The easiest way to do this is to create a symbolic link from the latter to the former. |
| | 70 | The easiest way is to use the [TranslateIntro BOINC Translation Service], a web-based system that's used for BOINC itself and for Einstein@home. |
| | 71 | If you want to add your project, get in touch with the person responsible for the translation service by sending an email to the [http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_loc boinc_loc@ssl.berkeley.edu] email list. |
