you could try this workflow:
- build your module/addin and use english as the core language because other languages do have display problems (like in german the umlauts)
- dialogues, item names and descriptions could use placeholders so that you are able to identify them later within the string editor
- after building your module/addin check in all your resources
- open up the string editor and check if all the needed resources are there
- export your module/addin and afterwards your talktable ("export talktable")
- you will get 3 talktables scattered around within the module's folders
- two of the 3 talktables have a suffix = _f and _c
i do believe that _f stands for foreign and _c is for core. the foreign language is always empty and can be deleted. the core talktable contains descriptions for skills, materials and so on. if you don't use custom ones this talktable can be deleted too. you just need the "your_modules_name_en-us.tlk"
- copy this tlk and rename it with the appropriate language suffix = e.g.: your_module_name_es-es.tlk for spanish
- drag'n drop this talktable within the toolset's window and it will open a node tree with all the string entries containing the english description
- rewrite all the entries and do the translation^^
- afterwards just save the tlk
- now place this tlk within the following folder:
your base tlk (modules_name_es-es.tlk) = my documents/bioware/dragon age/addins/modules_name/module/data/talktables
the core talktabe (modules_name_c_es-es.tlk, as said only useful if you are using custom skills and other custom core resources) = my documents/bioware/dragon age/addins/modules_name/core/data/talktables
- the last step is to push all your exported resources (like items, characters, dialogues and so on) through the flag patcher anakin5 provided and your are done
- now if you need other languages just grab your tlk, copy and rename it, drag'n drop within the toolset and rewrite all the entries
the tlktool is only needed if you are translating all the languages on the fly. i never used it and therefore it is not tested by me, although it may give you a more comfortable workflow. i like to do it manually
within the toolset's options you could also switch to another language but it seems that the toolset was never designed to use other string characters then the english ones or i am just too stupid^^
Modifié par -Semper-, 07 septembre 2010 - 12:12 .