Translating
To add a language or improve a translation, submit a pull request with a UTF-8 JSON file in i18next format, placed in packages/i18n/locales/.
Available translations
| Language | File in packages/i18n/locales/ |
|---|---|
| English (source catalog) | en.json |
| French | fr.json |
| German | de.json |
| Spanish | es-ES.json |
| Brazilian Portuguese | pt-BR.json |
| Polish | pl.json |
| Simplified Chinese | zh-CN.json |
To improve one of these languages, edit its existing file. These are the bot’s translations; the documentation is available in English and French.
Prepare the file
- Copy
packages/i18n/locales/en.json, the English source catalog. To correct an existing translation, edit its file directly. - Name the new file using the Discord locale code, for example
it.jsonfor Italian, which is not yet provided. - Translate every text value, preserving the file’s structure and source keys, including
_oneand_other. Add the plural forms required by the language (for example_fewand_manyfor Polish), keeping the same variables. - Submit the file in a pull request describing the language added or the corrections made.
Rules to follow
- Keep variables such as
,orwithout renaming or removing them. - Keep command names unchanged:
/picket settings,/timers add, etc. - Preserve Markdown and Discord tags, such as
**text**or<t::F>. - Keep command descriptions, option descriptions and choices within 100 characters; no translation should be empty.
CI checks keys, catalog coverage, variables and length limits. Once merged and deployed, the language appears in /picket settings → Language and is available in automatic mode. No code changes are needed.
