Differences

This shows you the differences between two versions of the page.

--- en:ds:rc_traduire_le_jeu [2018/08/06 14:21] – removed zatalyz
+++ en:ds:rc_traduire_le_jeu [2021/12/03 18:19] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== Translate the game ======
+{{ :fr:welcome-976277_640.jpg?direct&300 |Pixabay - CC0}}
+<WRAP center round info 60%>
+It's only the procedures description, if you want to discover the complete système, go on [[en:rc_localisation_traduction]].
+</WRAP>
+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.
+<WRAP center round todo 70%>
+The instruction's utilisation of ''_clean'' is missing, as well as :
+  * forget_phrase_diff
+  * inject_clause
+  * sort_trans_phrase
+  * make_worksheet_diff <filename>
+  * merge_worksheet_diff <filename>
+  * crop_lines <filename> <nbLines>
+  * extract_bot_names [-r]
+  * extract_new_sheet_names [-r]
+but are rarely used.
+</WRAP>
+===== Configuration tools =====
+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).
+===== Procedure =====
+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.
+==== Static client piece of data modification in wk.uxt ====
+It's the file wich help to display statics channels of the client (generally interfaces elements).
+Go on ''translation'' in the repertory and type :
+<code bash>
+$ translation_tools make_string_diff
+</code>
+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 :
+<code bash>
+$ translation_tools merge_string_diff
+</code>
+If all is allright, the file in ''diff'' is delete and its content is agregate in the ''translated'' file.
+So do again :
+<code bash>
+$ translation_tools make_string_diff
+</code>
+To generate the ''diff'' from the differents languages indicate to the system. Modify them all then relaunch the merge :
+<code bash>
+$ translation_tools merge_string_diff
+</code>
+==== Dynamic piece of data modification ====
+The other file concern the dynamic data's piece for the computer serveur.
+=== The ''phrases'' ===
+It's possible to create a file in the ''phrases'' ((sentences)) 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.
+<code bash>
+$ translation_tools make_phrase_diff
+</code>
+Then after translation :
+<code bash>
+$ translation_tools merge_phrase_diff
+</code>
+Then a second time to translate to the targeted language :
+<code bash>
+$ translation_tools make_phrase_diff
+</code>
+Then after translation :
+<code bash>
+$ translation_tools merge_phrase_diff
+</code>
+For the ''phrases'', an other file need to be created, called  the''clauses'' (also in two part) :
+<code bash>
+$ translation_tools make_clause_diff
+</code>
+Then after translation :
+<code bash>
+$ translation_tools merge_clause_diff
+</code>
+=== The ''words'' files ===
+Finally, there is still terms that arn't ''phrases'' but ''objet'' ((object)), ''titre'' ((tittle)) and others... Generally, all that is not in ''phrases'' but finish by ''words'' you have also to type :
+<WRAP center round important 75%>
+Be carefull about the edition of some of the dynamics files, like ''words'', which are .cvs file format, even if it's whrite .txt, and with input fields separate by a tabulation.
+</WRAP>
+<code bash>
+$ translation_tools make_words_diff
+</code>
+Then
+<code bash>
+$ translation_tools merge_words_diff
+</code>
+{{tag>traduction Ryzom_Core Serveur Client Tutoriel}}