Translation Team/Administration QuickStart: Difference between revisions

(7 intermediate revisions by 2 users not shown)

Line 9:

This page shows the current status of all translations for all files in a Project. Summary statistics along the top reveal the totals across all the files. For each file, a colored bar shows the progress of translations. It starts out in red color and becomes green when the translation is complete. The summary column shows the number of words that remains to be translated for this file. Selecting this link will take you to the first untranslated message for this file. The last column shows the current commit status. Don't depend on it fully. Sometimes, the status appears OK even when changes are not committed yet. This may be corrected in the future.

[[Image:Translate-overview.png]

[[Image:Translate-overview.png]]

From this overview page, the Language Administrator will be able to perform translations, review suggestions and approve suggestions from other translators, catch up with the latest message files, commit translations to the repository and then manage permissions for other Translators contributing to this project.

It is important that translations checked into the projects are from the latest message files, so we will start with that operation.

=== News and Events ===

The News section allows you to track changes happening in the Project like updates to translations, suggestions, commits, changes to VCS and so on. This page also allows to add your own message like vacation notices or hints to other translators.

[[Image:Translate-news.png]]

It is a good place to catch up with events after you return from a break or during intense activities.

=== Catching up with new strings to translate ===

Line 19:

Line 27:

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. Watch out for commit messages in the mailing list.

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".

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 press the link "rescan the project files" if any files have been added. Press the link "update the files from templates" if any existing files have been updated.

[[Image:Translate-files-top.png]]

Line 29:

Line 37:

While rescan and update templates links take effect immediately, Delete operations take effect only when you press "Save Changes". Otherwise the operation will be canceled.

=== Translate Messages for a Project ===

You can start translating messages for a file from the Overview, Translate or Review pages. For large files, selecting "Quick Translate" takes you to the first untranslated message in a file and skip already translated messages.

Once most of the translations are completed for a file, you need to Review it for errors before committing it to VCS. The commit links also appear here for convenience. You should really use the ones in the Review page where possible errors are displayed.

If translations have been checked into VCS meanwhile, you can update to the latest version file by file or all files (see below) from this page.

[[Image:Translate-translate1.png]]

For bulk edits like search and replace, it may be easier to download files, fix the messages and then upload or merge them back into Pootle taking due care not to overwrite any translations done by others in the interval.

~~===~~ Translate ~~Messages for a Project ===~~

You could also could add new translations as suggestions. These options appear at the bottom of the Translate section:

~~You can start translating messages for a file from the Overview,~~ Translate ~~or Review pages. Selecting "Quick Translate" takes you to the first untranslated message in a file~~.

[[Image:Translate-translate-bottom.png]]

~~[[Image:Translate-translate1~~.~~png|600px|center]]~~

Bulk uploads from version control can be done using "Upload all changes from version control" button. Use this with caution, as the risk of overwriting is quite high.

=== Translation Review ===

Line 41:

Line 60:

* To download the PO files, and go through it

* To run '--check' to ensure that the file is formatted correctly

* To use the various [~~[Localization~~/~~Testing#Utilizing_the_tests_available_from_within_Pootle|~~checks]] available from within Pootle

* To use the various [http://translate.sourceforge.net/wiki/toolkit/pofilter_tests checks] available from within Pootle:

Once the administrator is reasonably satisfied that the file is OK, she should go ahead and commit.

[[File:Translate-review-top.png]]

Once the administrator is reasonably satisfied that the file is OK, she should go ahead and commit:

[[File:Translate-review-commit.png]]

Wait for confirmation from the server before switching from this page.

=== Approval of Suggestions ===

Suggestions from other translators and anonymous users can be reviewed against each message. When a suggestion is selected by pressing the "correct" tickmark, its contents overwrite the current translation. You can edit it further if you like before pressing "Submit" and going to the next message. If you select "cancel" tickmark, the suggestion is rejected and deleted.

The "hassuggestion" hint appears along the top right when scanning through all suggestions. In this mode, pressing "Submit" will display the next pending suggestion. When all suggestions are reviewed, the "Review Suggestions" link at the top of the Review Summary will disappear.

~~=== Approval of suggestions ===~~

[[Image:Translate-review-suggestion.png]]

A summary of accepted and rejected suggestions appears at the end of Review summary.

=== Committing files ===

@@ Line 9: / Line 9: @@
 This page shows the current status of all translations for all files in a Project. Summary statistics along the top reveal the totals across all the files. For each file, a colored bar shows the progress of translations. It starts out in red color and becomes green when the translation is complete. The summary column shows the number of words that remains to be translated for this file. Selecting this link will take you to the first untranslated message for this file. The last column shows the current commit status. Don't depend on it fully. Sometimes, the status appears OK even when changes are not committed yet. This may be corrected in the future.
-[[Image:Translate-overview.png]
+[[Image:Translate-overview.png]]
 From this overview page, the Language Administrator will be able to perform translations, review suggestions and approve suggestions from other translators, catch up with the latest message files, commit translations to the repository and then manage permissions for other Translators contributing to this project.
 It is important that translations checked into the projects are from the latest message files, so we will start with that operation.
+=== News and Events ===
+The News section allows you to track changes happening in the Project like updates to translations, suggestions, commits, changes to VCS and so on. This page also allows to add your own message like vacation notices or hints to other translators.
+[[Image:Translate-news.png]]
+It is a good place to catch up with events after you return from a break or during intense activities.
 === Catching up with new strings to translate ===
@@ Line 19: / Line 27: @@
 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. Watch out for commit messages in the mailing list.
-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".
+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 press the link "rescan the project files" if any files have been added. Press the link "update the files from templates" if any existing files have been updated.
 [[Image:Translate-files-top.png]]
@@ Line 29: / Line 37: @@
 While rescan and update templates links take effect immediately, Delete operations take effect only when you press "Save Changes". Otherwise the operation will be canceled.
+=== Translate Messages for a Project ===
+You can start translating messages for a file from the Overview, Translate or Review pages. For large files, selecting "Quick Translate" takes you to the first untranslated message in a file and skip already translated messages.
+Once most of the translations are completed for a file, you need to Review it for errors before committing it to VCS. The commit links also appear here for convenience. You should really use the ones in the Review page where possible errors are displayed.
+If translations have been checked into VCS meanwhile, you can update to the latest version file by file or all files (see below) from this page.
+[[Image:Translate-translate1.png]]
+For bulk edits like search and replace, it may be easier to download files, fix the messages and then upload or merge them back into Pootle taking due care not to overwrite any translations done by others in the interval.
-=== Translate Messages for a Project ===
+You could also could add new translations as suggestions. These options appear at the bottom of the Translate section:
-You can start translating messages for a file from the Overview, Translate or Review pages. Selecting "Quick Translate" takes you to the first untranslated message in a file.
+[[Image:Translate-translate-bottom.png]]
-[[Image:Translate-translate1.png|600px|center]]
+Bulk uploads from version control can be done using "Upload all changes from version control" button. Use this with caution, as the risk of overwriting is quite high.
 === Translation Review ===
@@ Line 41: / Line 60: @@
 * To download the PO files, and go through it
 * To run '--check' to ensure that the file is formatted correctly
-* To use the various [[Localization/Testing#Utilizing_the_tests_available_from_within_Pootle|checks]] available from within Pootle
+* To use the various [http://translate.sourceforge.net/wiki/toolkit/pofilter_tests checks] available from within Pootle:
-Once the administrator is reasonably satisfied that the file is OK, she should go ahead and commit.
+[[File:Translate-review-top.png]]
+Once the administrator is reasonably satisfied that the file is OK, she should go ahead and commit:
+[[File:Translate-review-commit.png]]
+Wait for confirmation from the server before switching from this page.
+=== Approval of Suggestions ===
+Suggestions from other translators and anonymous users can be reviewed against each message. When a suggestion is selected by pressing the "correct" tickmark, its contents overwrite the current translation. You can edit it further if you like before pressing "Submit" and going to the next message. If you select "cancel" tickmark, the suggestion is rejected and deleted.
+The "hassuggestion" hint appears along the top right when scanning through all suggestions. In this mode, pressing "Submit" will display the next pending suggestion. When all suggestions are reviewed, the "Review Suggestions" link at the top of the Review Summary will disappear.
-=== Approval of suggestions ===
+[[Image:Translate-review-suggestion.png]]
+A summary of accepted and rejected suggestions appears at the end of Review summary.
 === Committing files ===