Open your browser and go to http://i18n.redhat.com/cgi-bin/i18n-status. Select a language, and a web page similar to Figure 32, “Take a File for Translation” appears. In this example, the PO file in package dist has 839 entries untranslated and not taken by any translator. To claim this file, press the Take link at the right hand side.

Figure 32. Take a File for Translation

If the file is not available for translation because someone else is working on it, the status appears as Assigned, as shown in Figure 33, “File Has Been Taken”.

Figure 33. File Has Been Taken

After you click the Take link, a prompt appears for your username and password as shown in Figure 34, “Username and Password Prompt”. Enter your login name and PIN code as described in Figure 12, “Example Email”.

Figure 34. Username and Password Prompt

The system assigns the file to you after you successfully login, as shown in Figure 35, “File is Assigned to You”, or it displays an error page upon unsuccessful login, as shown in Figure 36, “Authentication Failed”. Please email mailto:i18n@redhat.com to request a reissued PIN code if you lose your PIN.

Figure 35. File is Assigned to You

Figure 36. Authentication Failed

To download the latest files from server, right-click the translate folder in Windows Explorer and select CVS Update. A prompt appears for the passphrase of your private key before TortoiseCVS can continue as shown in Figure 37, “Get Update Files from CVS”.

Figure 37. Get Update Files from CVS

A screen appears similar to Figure 38, “Update Successful” after the update successfully finishes. The letter "P" in front of any file stands for "patched," which means minor changes from the server had been patched to your files. A letter "U" stands for "updated," which means your file is overwritten by the latest version due to major changes. Do not panic if you see "P" and "U." Since translation is done through collaboration, the files are bound to change occasionally. As long as you have committed your changes, your version is never lost, which is a benefit of using CVS.

Figure 38. Update Successful

Open the file you took and downloaded from the server. Either double-click on the .po file, or open the .po file within the poEdit application. Remember to save your changes when you finish translating.

Uploading the file you have translated back to the CVS server is similar to the download operation. Right-click on the translate folder in Windows Explorer and select CVS Update. A prompt appears to enter the passphrase of your private key before TortoiseCVS can continue. After you correctly input your passphrase, a screen appears similar to Figure 39, “Update Before Commit”.

Figure 39. Update Before Commit

"M" stands for "modified". It indicates that this file was modified on your local machine and needed to be uploaded to server.

If you see a capital "C" instead of "M", as shown in Figure 40, “File Conflict”, then a conflict has occurred. A conflict occurs if you modify part of your local file while the same part of the same file on the CVS server is changed at the same time. Conflicts may be caused by:

You must resolve file conflicts manually. Conflicts may cause lost translation and wasted effort. Please seek assistance through your translation community and relevant mailing lists.

Figure 40. File Conflict

If everything is fine, upload the file you modified. Choose CVS Commit after you right-click on the translate folder, as shown in Figure 41, “Commit Files to Server”.

	Updating and Committing
	A CVS update will notify you about file modification on your local computer. It will not, however, upload the file back to server until you choose to perform a CVS commit.

Figure 41. Commit Files to Server

A list of modified files appears, as shown in Figure 42, “Commit Files to Server”. Check the files you plan to upload to the server. You should add some relevant comments, so other translators can easily track what has been changed in any file. Press OK to upload the file.

Figure 42. Commit Files to Server

A prompt appears for the passphrase of your private key. After files are successfully uploaded to server, a screen appears similar to Figure 43, “Commit Files to Server Successfully”.

Figure 43. Commit Files to Server Successfully

This phase is optional, and only occurs when you stop working on a file before it is fully translated. For example, you may go on a holiday, but would like others to be able to resume the work. To do so, visit the Fedora status page, find the package you previously took, and click the package name to view the detail. On the bottom of that page, a Release link appears, as shown in Figure 44, “Release File Screen”.

Figure 44. Release File Screen

This is the end of the life cycle of Fedora software translation. We do hope you enjoy being with part of the open source community and continue lending your support.