Ellpeck/TinyLifeWeb
1
0
Fork 0
mirror of https://github.com/Ellpeck/TinyLifeWeb.git synced 2024-11-26 04:48:34 +01:00
Code Issues Projects Releases Wiki Activity

elaborate on the verbose argument for translation testing

Browse source
This commit is contained in:
Ell 2024-04-28 20:20:27 +02:00
parent f075f57fa7
commit 5f1b877f90
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/articles/localization.md
View file

@ -31,7 +31,9 @@ First of all: Please don't feel obligated to finish the translation for the lang
*For example, in `You can rotate furniture by pressing <k Rotate>.`, the formatting code will be replaced with the key value of the keybind to rotate furniture and other objects. If the word `Rotate` in it was changed (or translated), the link to the keybind would be broken.* *For example, in `You can rotate furniture by pressing <k Rotate>.`, the formatting code will be replaced with the key value of the keybind to rotate furniture and other objects. If the word `Rotate` in it was changed (or translated), the link to the keybind would be broken.*
### Testing Your Translations ### Testing Your Translations
To test your translation, you can export it and put it into the game. To export it, head to the "Files" section in the left sidebar, and then press the `Localization.json` file's export button, which looks like a little cardboard box. In the menu that comes up, select the language you're working on from the dropdown, and leave everything else the same. Now, you can put the exported file into the `Content/Localization` folder of the game's installation. If it's not part of it already, its name also has to be added to the `LanguageNames.json` file. Starting the game with the `-v` argument will cause it to output some additional information about errors in your localization to the [log file](game_dir.md) as well. To test your translation, you can export it and put it into the game. To export it, head to the "Files" section in the left sidebar, and then press the `Localization.json` file's export button, which looks like a little cardboard box. In the menu that comes up, select the language you're working on from the dropdown, and leave everything else the same. Now, you can put the exported file into the `Content/Localization` folder of the game's installation. If it's not part of it already, its name also has to be added to the `LanguageNames.json` file.
It's highly recommended to start the game with the `-v` (or `--verbose`) argument, as that will cause it to output some additional information about errors in your localization to the game's [log file](game_dir.md). Fixing errors like these is generally very important, as they can cause players to receive incorrect or incomplete information or, in some cases, cause the game to crash.
### Language Overrides ### Language Overrides
Strings that begin with `Overrides` are part of the overrides section, which is a set of settings that determine the way parts of the game operate when a language is applied. These should not be translated, and set to the appropriate values instead. Strings that begin with `Overrides` are part of the overrides section, which is a set of settings that determine the way parts of the game operate when a language is applied. These should not be translated, and set to the appropriate values instead.