Google Code-In 2012/Activity i18n

The following activities are in need of being re-factored to include internationalization (i18n). What this means is modifying the code so that strings that appear in the user interface are specially marked for recognition by the gettext tools allowing them to be extracted into a POT (portable object template) file.

POT files are the uploaded to the translation server (Pootle) by a process that results in linking the code repository to the Pootle server so that additional changes in the UI strings are automatically incorporated into a refreshed POT file and when translations are completed on the Pootle server, the PO files are committed to the repository in it's /po directory where they are used during the build process to create MO files that present the translated strings to users.

Activities developed in Spanish
The task mentor will provide help with the Spanish to English translation of the Ui strings.


 * JAMedia (flavio)
 * CucaraSims (flavio)
 * Conozco Elementos Químicos (ChristoferR)
 * CantaBichos (flavio)
 * Ecomundo (gonzalo)
 * Domino (gonzalo)
 * Conozco Peru (javier2dc)

Activities developed in English

 * StarChart (davewa, cRiSgOd)
 * ConstellationsFlashCards (davewa)
 * Theorie (frasene)
 * Free Cell (bertf)

The modification process:

1) Find the code repository in git

2) Create a branch with an easily recognized name (e.g. i18n branch).

3) Modify the code to mark the UI strings for getext extraction, call the gettext function.

See http://en.flossmanuals.net/make-your-own-sugar-activities/going-international-with-pootle/ for a description of the i18n process.

4) Generate the POT file and place it in the /po directory. If being ported from Spanish, create an es.po file containing the original Spanish language strings.

5) File a merge request with the repository maintainer. Request that they make gituser: pootle a commiter on the repository

6) File a ticket in the bug tracker with component = "localization" requesting that the activity be set up in Pootle. Be sure to include a link to the main repository page.