Updated Translations (markdown)

FlyingPikachu 2017-07-23 23:55:32 -04:00
parent 418603aec7
commit af6cc164ee

@ -12,7 +12,7 @@ Here are some tips to follow when editing the language file:
* Keep the double quotation marks on the ends of each translation
* Do not use double quotation marks in any of your translations or you will likely break them. You can use single quotes however.
* 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 using words other than "player" and "quest" will not work.
* 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 will not 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.