Improve SiT by translating it
How to translate editing the language file
Preferably you should copy the <sit-root>/i18n/en-GB.inc.php to the language code you are translating to; en lowercase is the language, GB upper case is the country.
You can use any editor you want as long as it can save in UTF8, an editor with highlighting is recommended.
Some free editors for different operating systems which can handle this.
- Make sure that each text string is within apostrophes. Example :
- Make sure that each line ends with a semicolon. Example :
$strSomeText = 'some text';
How to translate from within SiT!
In the first page you have the choice of selecting which language you want to translate into (selection box to the right), but also the choice of which language to translate from (selection box to the left). The translate from part should only be used if the translate from language is 100% complete.
It's probably best to translate from English (British) where possible but you can translate from one of the languages that has been fully translated if this is easier for you.
During translations you want to jump to the next untranslated string. Use your browsers search, and search for a * this helps you to get to the next untranslated string as well.
Some notes has been added in several places, helping you to understand the meaning of the following word, this is due to that some English words have multiple meanings.
Because the translation table is quite big, and translating on the windows platform is very slow a bug of pagination the translation page has been added.
|A bug has been reported that affects this functionality: Translation page should be paginated|
There are several help files that needs translation aswell.
These files are stored in subfolders in <sit-root>/help/ copy the en-GB folder to your language. and simply edit the files with a text editor, replacing the original text.
The files needs to be saved in UTF8 format.
How to submit your translations
There are a couple of ways for you to submit your translations.
- Attach them in an email and send them to Ivan Lucas ivanlucas[at]sitracker.org
- If you have access to committing to SVN, you can commit there.
The are a couple of ways to get help