[X] Double checked existing Issues/Pull Requests for a similar suggestion.
Describe the change you would like to see
Rewrite i18n stuff to supply a more universal and cleaner approach to translating TrixieBot.
Why should we change it that way?
Currently i18n required manipulation of built-in discord.js class prototypes, adding properties to discord.js Objects and having the translation phrases in the code be exactly the same as in the translations, which reduced readibility of the locale files, increased junk and didn't make it clear what is translatable and what is not.
Before submitting I have
Describe the change you would like to see Rewrite i18n stuff to supply a more universal and cleaner approach to translating TrixieBot.
Why should we change it that way? Currently i18n required manipulation of built-in discord.js class prototypes, adding properties to discord.js Objects and having the translation phrases in the code be exactly the same as in the translations, which reduced readibility of the locale files, increased junk and didn't make it clear what is translatable and what is not.