First and foremost thank you for your interest in contributing to this project. To translate this project it is easier to work directly with the source code – follow the guide how to run this software from source in the installation guide. In most cases before you translate, it’s best to contact the eduActiv8 developer first to make sure that nobody else is working on the translation but also to get your language added to the program, this will make it easier to test the translation as you go, alternatively you can just pick an existing language and replace it with yours or use the te_ST.po and te_ST.py which is there for that purpose, but unfortunately the text-to-speak will not work until it’s properly configured for your language.
There is only a couple of files to translate. The language files (source) are stored in the i18n/ directory. The main files are located in the po/ directory, however, some features that were rather hard to be extracted into the po files are located in language files in custom/ directory. In most cases, you do not need to worry about anything in the kbrd/ and word_lists/ – these are usually done by the developer.
To edit the *.po files it’s best to use the Poedit program – it’s very easy to use and creates a compiled *.mo file for you after saving which is pretty convenient because this is the file the program uses. When you complete the translation the *.mo file needs to be moved to the language-specific directory in locale/. If you run the cleanup.py program it will automatically move all compiled translations for you and also remove all temporary files making the project ready for packaging. You can usually run it by double-clicking or alternatively via console (by executing python cleanup.py on Linux).
The custom file is a bit harder because you are essentially editing a python source file. The comments, starting with #, do not need to be translated but in most cases explain how a piece of code that follows a comment needs to be translated. One of the things involves typing the alphabet in your language and then finding words starting with each letter of the alphabet. The tricky bit is that words need to describe images in res/images/fc/ which are referred by the number of an image the word is representing. Obviously not always it will be possible to match all letters to existing images so new images may need to be added. The first place to look for the images would be in res/images/art4apps/. Also, there may be a case that no word starts with a particular letter, in such case any word can be used as long as it contains the letter somewhere.
There are also 2 functions there, one of them returns numbers as text (spelt out), the other one returns time as it is read. If you are not sure how to go about changing those please just write the rules how it’s done for 0-100 and also how you read time in your language. You may also have a look at other languages to get a rough idea how to do it.
At the end of the custom file you will find 12 lists/categories of words. If translated the word building and word listening activities will not only appear in the English language but also in the language you are translating the program to. Could be pretty useful, even though the software will work without it, the language section will be rather limited, anyway if you can spare some more time it’s 589 words to translate. One way to go about it would be to translate it with Google Translate and then correct the bad translations (making sure the word matches the corresponding image in the res/images/art4apps/) and it’s going to be quite a few of the bad ones. Google Translate tends to reorder the words so it’s important to make sure they are still in the same order.
Please also remember to stay in touch if you get stuck at any point.