Difference between revisions of "Translation Team/Administration QuickStart"
| Line 43: | Line 43: | ||
..and you are done. | ..and you are done. | ||
| + | |||
| + | === Catching up with new strings to translate === | ||
| + | |||
| + | Developers will be modifying the strings that need to be translated as they implement features and fix bugs. It can happen at any point in the release cycle but less so during the [[Development_Team/Release#String_cooling|string cooling]] and [[Development_Team/Release#String_Freeze|string freeze] periods. | ||
| + | |||
| + | To tell Pootle that it needs to pick up those changes, the language administrator for that project needs to go to the Files tab and run the links "rescan the project files" and "update the files from templates". | ||
== References and links == | == References and links == | ||
<references/> | <references/> | ||
Revision as of 02:38, 29 September 2010
| Please copy/paste "{{Translationlist | xx | origlang=en | translated={{{translated}}}}}" (where xx is Translation Team/ISO 639 language code for your translation) to Translation Team/Administration QuickStart/translations | HowTo [ID# 57646] +/- |
This page is a work in progress, please feel free to work upon it, and improve it
Pootle administrators have extended privileges over normal translators. They can grant or revoke permissions for normal Pootle registered users on a project wide basis, and can also add other administrators for their particular project. Note that administrators are specific to the combination of project and language, which means that [ Spanish ] [Honey] can have a totally different set of administrators and privileged users than [ Spanish ] [ Fructose ], or of course, [ Amharic ] [ Honey ].
The typical roles of a language administrator
Administrators have a few well defined responsibilities. Areas of responsibility are:
- User management
- Translation review
- Approval of suggestions (optional)
- Committing of translations
User Management
TBD
Translation Review
Before the administrator commits a particular file, she must make sure that the translations are OK. There are several way to do this, one of them would be
- To download the PO files, and go through it
- To run '--check' to ensure that the file is formatted correctly
- To use the various checks available from within Pootle
Once the administrator is reasonably satisfied that the file is OK, she should go ahead and commit.
Approval of suggestions
TBD
Committing files
The final step in ensuring that the translations are merged back into the master source tree of the software is to "Commit" them. Committing is a pretty straightforward process, but you should ideally do it only after you have done the relevant checks and reviews. We recommend that you follow a 'release early and release often policy'[1] while committing, as that would get the maximum amount of exposure and testing for your translations.
To Commit, you will have to first click on the "Show Editing Functions" link in your main project page (the page which shows the list of PO files).
Once the Show Editing Functions link is activated, click on the "Commit" link below each PO file you want to commit.
..and you are done.
Catching up with new strings to translate
Developers will be modifying the strings that need to be translated as they implement features and fix bugs. It can happen at any point in the release cycle but less so during the string cooling and [[Development_Team/Release#String_Freeze|string freeze] periods.
To tell Pootle that it needs to pick up those changes, the language administrator for that project needs to go to the Files tab and run the links "rescan the project files" and "update the files from templates".