Language variables as separate locale files #5456
Unanswered
tester43214
asked this question in
Ideas and Feature Suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I would suggest getting all plugin internal translations out to a separate locale files (like yml). This is because all the translations along with colours are hard coded into the plugin, leaving no possibility to match them with a chosen in-game colour styling.
Or better, make some kind of "translatable aliases" available to give people possibility to replace that hard coded colouring with a chosen one. I think it could be the additional file with translation keys in it (initially with no values so the default strings are displayed) and when I replace "" (empty string) with my own string, it will replace the original hard coded value. Eg.:
balance: "" <---- this is the default line inside that additional translation file, which results in displaying green word "Balance" and red value of balance (default for EssentialsX)
balance: "$fBalance: $a{0}" <---- this results in replacing the default string and displaying white word "Balance" and green value of balance (custom view).
Someone else has already pointed to the fact that hard coded colours were not updated for long time (#5039) but I would like a bit more so the EssentialsX plugin would become much more flexible for its users. I am ready to pay for the "premium" work if you are able to add such a feature.
Beta Was this translation helpful? Give feedback.
All reactions