Hacking:Localization

This file contains some important hints for translators.

The current status of the Valentina translation can be checked at https://www.transifex.com/valentina/valentina-project/

Translation of the Valentina is handled by the Valentina translation team (see https://www.transifex.com/valentina/teams/7274/). If you want to help, create an account on Transifex and make a request to join the team.

We recommend this short video with Transifex Translation Editor Tutorial.

The more progress we make the more complex Valentina became. There are several thing you should know before you will start your work.

Add new language
If you don't see your language already in the list you can create a language request. But be sure that your request contains not only language code, but also country code. Example of correct codes: en_US, en_CA, en_IN, ru_RU, de_DE. Wrong requests: nl, uk, ja etc.

Several source files
At the same time transifex can have several source files that represent different branches of code. Source file without number "valentina.ts" represent last unstable changes in code. This file unstable and can be changed many times before the release. Translations from this source you will find in each unstable installer we provide.

From the other side source file "valentina_0_2_9.ts" represent stable release. Strings from this source file will almost never disappears. Fixes in this source file will be used in new minor release with bug fixes.

Which source file prefer to take? Main goal translate all strings. So we recommend begin work with "stable" source file and then update "unstable" just by uploading them like unstable on Transifex. Most time they have more than 90% similar strings. System yourself clean all "old" string that already do not exist in this source file.

Internationalizing Valentina
You should remember several aspects when you translate Valentina.


 * Do not translate strings that you don't understand!!
 * Valentina support language independent measurements. And not all measurements can be easy translated don't do anything if you not sure about translation.
 * Some text contain special characters that you should left without translation.
 * Translate only text.

Applying translation
You do not need to do anything. One of developers will download all changes and apply it.

But in case you build the project from source code you need to do additional moves.
 * Check if after you last edit of localization someone applied it. Try to find commit with comment "Lupdate" in appropriate branch. Usually develop or release. Don't forget compare dates.
 * Update to a branch head.
 * Call Clean All.
 * Call Run qmake.
 * Call Build All.

Common mistakes

 * Space letter inside measurement name.
 * Missed place holder i.e. %1, %2 ... %99. For example instead of %1 a string has 1%. Or doesn't have at all.