-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: command locales #9
Comments
All locales should have a json file in the directory All translations should include the same keys as |
Formatting for command entries is as follows: {
"<COMMAND>_NAME": "The name of the command",
"<COMMAND>_DESCRIPTION": "The description of the command",
"<COMMAND>_ARG_<ARGUMENT>_NAME": "The name of this argument",
"<COMMAND>_ARG_<ARGUMENT>_DESCRIPTION": "The description of this argument"
} N.B. Keys should be all caps. |
If you are unable to complete a translation, rather then remove the key please just leave the |
We will also require manually localizing all strings sent within commands and error handlers. |
(Linked the PR to the wrong issue) |
* refactor: clean up suggestion message finalization * feat: localize suggestions commands #9 * feat: add message commands for handling suggestions * feat: remove clear as a message command * fix: stats enum for message commands * fix: translations newlines * fix: tests & PR template * doc: bump bot version * chore: resolve reviews
Format for localizing embeds: {
"<CMD>_INNER_<VARIABLE>_EMBED_<FIELD>": ""
} |
This is simply an issue used to track localization progress over time in a centralized location.
The text was updated successfully, but these errors were encountered: