Fortnite: Save The World Discord bot.
This repository is meant to house all the Language files used in See-Bot.
You are welcome to contribute translations of the strings to improve See-Bot's (planned) Localization. If you plan on contributing to the project, please read the outline below.
- Pick a language you're fluent in
- Download the project (fork a copy of it)
- Translate the English properties files to your desired language, preserving markdown and variables (See "Formatting Help" below)
- Rename each file you translate to include the appropriate Language Code at the end of the file name, before the file extension (See "Naming Help" below)
- Make a pull request containing the updated Localization files.
So you've decided you want to translate a file, but you don't know what you should and shouldn't be changing. Let's start by taking a look some examples:
KeyOne=This is a value with `markdown` and variables %arg0%.
KeyTwo=This is just a normal value.
#This is a comment.
Taking a look at the start of each line, you can see they start with a word (or phrase) followed by an equals sign. This is a Key. Everything after the equals sign is the Value. DO NOT modify Key names, or else See-Bot won't be able to find the Value associated with it anymore.
In KeyOne, it uses a mixture of Discord Markdown and variables. The text %arg0% is a variable that gets replaced programatically by See-Bot, filling it in with a changing-value (example: A Fortnite Username, which is different for each user).
In KeyTwo, it has no markdown or variables, for comparison.
Other things to avoid removing/translating are unicode characters, line breaks, and other code escape sequences. Examples of these include \u3242 \n \r \t \\. Removing/translating these will break formatting or emojis that the bot uses.
Lines starting with # are comments, and do not get read by the bot. Do not modify comments. You are welcome to add your own comment in files you worked on (i.e: #File edited by HighHowDoIPlay). Don't claim others' work as your own.
When modifying a .properties file, it is recommended to use Notepad++ or a similar Rich-Text-Editor. This will help you easily distinguish between what is and isn't a key, and just provide an easier editing experience overall.
NOTE: Please be sure to check back here often, as I may the help information/"rules" on submitting.
You're also welcome to Join the See-Bot Discord, where I'll be posting updates and etc about the project.
You've downloaded the English Language files, have started to translate them but now you don't know what to save the file name as.
- First, you'll want to open the Discord Supported Locales webpage.
- Then, you'll want to find the Language you've decided to translate. We'll use
English, UK, as an example. - Next, find the language tag (4th row). For our example, it's
en-GB. This is what you'll be including in the file name, but you will need to make some modifications first. - Add a _before the start of the tag, and replace the - with a _ as well. Then, change any uppercase letters to lowercase.
en-GBbecomes_en_gbin the example. - Add your new language tag to any file you translate. For example, if you updated
CommonStrings.propertiesto have English translations for the UK, you'd update the file name toCommonStrings_en_gb.properties.
If you still need assistance Join the See-Bot Discord, and ask for help in the #properties-help channel.
If you see a "MissingKeys" error in See-Bot, it's due to one of the following:
- I copy and pasted some code and forgot to change what file the Language Handler is pointing to.
- The key is misnamed in the properties file.
- The key is misnamed in the code.
If it's issue 1 or issue 3, it's best to contact me on the See-Bot Discord (above) and tell me what is broken. If it's issue 2, then you should make a pull request with the fix before contacting me, or if you don't know how to do that, just contact me on the See-Bot Discord.