-
Notifications
You must be signed in to change notification settings - Fork 105
Translations
This article explains how to create translations for the Valkyrie app itself and for scenarios/quests.
Translation data for Valkyrie can be found in:
<install location>\valkyrie_Data\StreamingAssets\text
These files can be edited with a text editor and tested with Valkyrie. To submit changes open a new issue and attach the file, or submit a pull request if you know how to do so. Additional languages require a Valkyrie change, and can be tested by replacing one of the supported languages.
MoM content packs have some additional language data here:
%userprofile%\Documents\valkyrie\valkyrie\build\batch\valkyrie_Data\StreamingAssets\content\MoM\base
Submit changes as above, additional language files are added into content_pack.ini
Each quest has a set of Localization files that can be translated. Any text edited in Valkyrie will be saved as your current language setting. Please see the author for submitting translations.
If you are the owner of the scenario you can directly open the scenario folder and open one of the translations files. If you are not the owner the scenario you need to download the scenario from scenario list in valkyrie and afterwards go to %userprofile%\AppData\Roaming\Valkyrie\Download and afterwards unpack (e.g. using 7zip or build in unpack tools) the scenario file you want to translate (e.g. MyScenario.valkyrie).
The translation files have lines in the format <key>,<value>. The first line of a translation file should start with .,<language name> (for example .,German for a german translation file). In most scenarios the Localization.English.txt file is the master file. All keys that are missing in the child files (for example Localization.German.txt) will be taken from the master file. That's the reason, why most child files are much smaller. In most of the cases all lines with the value {qst:<key>} don't have to be copied to the child file. All lines that don't need to be translated, don't need to be copied over. Make sure to add your language file to the quest.ini:
[Quest]
...
defaultlanguage=English
...
[QuestText]
Localization.English.txt
Localization.Spanish.txt
Localization.German.txt
Localization.French.txt
...
If a scenario has only the master file and no child files, it is a good idea to rework the master file and replace all double values with {qst:<key>} references and add new lines with unique keys for values that appear a lot like "Continue".
To replace Pictures and audio content (supported in V2.2)
You can add translation for your audio and pictures by adding a new directory per languages in your scenario directory. Files should have the exact same name as the file they should replace.
Example: You create scenario in your native language (this would be the default language for your scenario)
-- [Scenario1]
----- quest.ini (default language - your native language)`
----- events.ini (path to file)`
----- UI.ini (path to file)`
----- sound1.ogg (your native language)`
----- image1.jpg (your native language)`
next you want add translate
-- [Scenario1]
----- quest.ini (default language - your native language, add new language)
----- events.ini (path to file)
----- UI.ini (path to file)
----- sound1.ogg (your native language)
----- image1.jpg (your native language)
----- [New language] (example Spanish, create new folder "Spanish")
--------- sound1.ogg (add file)
--------- image1.jpg (add file)
A scenario example is available here : https://drive.google.com/open?id=1C2x_lnVFHzRpt9JmsKC6c1B8XNCIcT3l