Skip to content

TronixDev/Soundy-Languages

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 

Repository files navigation

Translations

How to Add a New Language

  1. 📁 Create a new file in the locales directory with the name of the language in the format language_code.json. For example, en-US.json for English, ms-MY.json for Melayu and etc.
  2. 📋 Copy the contents of the en-US.json file into the new file.
  3. 🌐 Translate the strings in the new file to the desired language.

Current Translators

  • English (US) - en-US.json (Default)
  • Indonesian - id-ID.json by @iaMJ
  • Japanese - ja-JP.json by @iaMJ (Not Accurate)
  • Polish - pl-PL.json by @JellyTyan

Translation Rules

  1. 🔒 Do NOT translate or modify any text within double curly braces {{}}. These are variables that will be replaced with actual values.

    • Example: "{{prefix}}play" must stay as "{{prefix}}play"
    • Example: "Page {{current}}/{{total}}" must stay as "Page {{current}}/{{total}}"
  2. 🔗 Do NOT translate or modify markdown links [text](url).

    • Example: [here](https://discord.com/...) - translate only "here", URL must stay unchanged
  3. ✨ Keep all formatting symbols like **, *, \n, etc.

    • Example: "**Hello!**" - translate only "Hello", ** must stay
    • Example: "Line 1\nLine 2" - \n must stay for line breaks
  4. 🎯 Keep the same JSON structure and keys, only translate the values.

    {
      "key": "Translate this value",
      "nested": {
        "key": "Translate this value"
      }
    }
  5. 📝 Keep command names exactly as they are.

    • Example: /play, /help, /bassboost must stay unchanged
  6. 🚫 Do not add or delete any JSON keys - only translate the values.

  7. ✅ Make sure JSON syntax stays valid after translation.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published