Updated Translations (markdown)

FlyingPikachu 2018-12-01 12:33:23 -05:00
parent 3048630f20
commit 65d6b50e15

@ -19,8 +19,7 @@ Here are some tips to follow when editing a language file:
* Do not change anything in < >'s. This is special data that later gets replaced by something else when the translation is accessed. You are welcome to move it around, but it cannot be translated. For example, "`<player>` has forcibly started the Quest `<quest>`." could be modified to something like, "The Quest `<quest>` has been given to player `<player>`" but translating the `<player>` and `<quest>` tags to another language won't work.
* Feel free to use regular brackets and parentheses in your translations.
* All of the Quests command translations are prefixed with COMMAND_ and are in all caps. You can change the specific Quests commands like list, take and quit, but you cannot change the /quests, /quest and /questadmin commands to anything else. Make sure to change the help displays for each of them if you change them.
* If you change the 'cmdCancel', 'cmdClear' etc. translations, make sure to change the translations that have things like "or enter 'cancel' to return" to match your new cancel command.
* Things that are lowercase are meant to be that way for formatting purposes. You can change it to uppercase if you want but it won't look pretty afterwards.
* Strings that start lowercase are meant to be that way for formatting purposes. You can change it to uppercase if you want but it won't look pretty afterwards.
If you are ever unsure about whether or not your edits are correct, or you receive errors on startup, try using an online YAML parser to check your language file. One such parser can be found [here](http://yaml-online-parser.appspot.com/).