Translate the game

The procedure to translate the differents game elements is quite simple but ask a quite strict respect to avoid the troubles.

It's generally done in two part : one to generate the referent version work in translated then an other to generate the diff in the others languages and include the news translate terms.

Generally speaking, it's better to translate little part by little part to avoid to keep big files still in progress in diff. In the aim to avoid potential functioning problem of the translate pipeline.

Go on khanat-ressources/translation

Configure translation_tools.cfg

Verify that translation-tools is well installed : it's an exectutable files link to the Nel tools compilation. Put it in a repertory where it can be find from anywhere from the computer (for exemple a /scripts_persos repertory on the root of its personal repertory and indicate to the system as a exectuable).

When news files are drop in the repertory work or just modified, differents translation tools command can be use according to the files.

Never change manually a file outside of the work or diff repertory and absolutely never directly on the generate file of translated. It's the best way to obstruct the translation pipeline.

The indicate commands are always launch from the translation repertory. It's where you can also find the languages.txt file (which contain language's code to manage) and the translation_tools.cgf to adopt under the configuration.

It's the file wich help to display statics channels of the client (generally interfaces elements).

Go on translation in the repertory and type :

$ translation_tools make_string_diff

To create the diff of the wk version, go in the diff repertory and correct/complete.

Then go back in the translation repertory and type :

$ translation_tools merge_string_diff

If all is allright, the file in diff is delete and its content is agregate in the translated file.

So do again :

$ translation_tools make_string_diff

To generate the diff from the differents languages indicate to the system. Modify them all then relaunch the merge :

$ translation_tools merge_string_diff

The other file concern the dynamic data's piece for the computer serveur.

It's possible to create a file in the phrases ¹⁾ subdirectory to tide its personal gestion. Just need to verify the reference in the “phrase_wk.txt” to be sure to be registered. If new phrase file are created in the phrases subdirectory, it must be specified. There will be not un big file generate at the end but it's possible to have as much little file as you want.

Outside this, it's the same procedure, in two part, with make_diff then merge_diff at each time.

$ translation_tools make_phrase_diff

Then after translation :

$ translation_tools merge_phrase_diff

Then a second time to translate to the targeted language :

$ translation_tools make_phrase_diff

Then after translation :

$ translation_tools merge_phrase_diff

For the phrases, an other file need to be created, called theclauses (also in two part) :

$ translation_tools make_clause_diff

Then after translation :

$ translation_tools merge_clause_diff

Finally, there is still terms that arn't phrases but objet ²⁾, titre ³⁾ and others… Generally, all that is not in phrases but finish by words you have also to type :

$ translation_tools make_words_diff

Then

$ translation_tools merge_words_diff