How translations work
New or changed English text is translated into every supported language by a workflow, which opens a pull request titled ”🌐 Update translations”. The workflow runs whenever English text changes on the main branch, so a translation usually appears within a few hours of the English text being merged. Each translation is checked before it is accepted: variables, tags and plural rules must match the English text. A glossary keeps product terms consistent within each language. It lives ini18n/glossary.json and lists how terms such as “Space” or “Event Types” are translated, plus names that are never translated, such as “Rallly” and “Pro”.
Correcting a translation
If a translation is wrong or reads awkwardly, edit it directly and open a pull request. Translations live in JSON files, one folder per language:
Each JSON file maps a key to its text. Find the key by searching for the English text in the matching file under
en, then change the value in your language’s file.
A blog post is translated as a whole Markdown file. Edit the text, but keep links, images, code and components such as <FaqItem> exactly as they are in the English post, or the check rejects the file.
Your correction is kept. The workflow only translates a string again when its English text changes, and it uses your version as a starting point when it does.
If a term is translated inconsistently across many strings, fix the existing strings and add the term to the glossary in the same pull request. The glossary only guides future translations; it doesn’t change strings that are already translated.
Tips for translators
Here are a few things to keep in mind when editing a translation.Punctuation
Pay close attention to how phrases are punctuated.Variables
Variables are placeholders for content that can change. They look like this:{name} is replaced with the user’s name. Leave variables unchanged.
Tags
Tags create a link or change how some text looks (for example bold or italics). They look like this:Plurals
We use ICU message format
for plurals.
1, or 2 options for anything else:
# is a placeholder for the value of count.
If your language needs more plural forms, add them. Every plural must keep its other case, and any exact number cases such as =0.
Register
For languages with informal and formal registers, use the informal register unless your language’s existing translations do otherwise. If you’re not sure, please reach out.FAQ
What if I don't see my language?
What if I don't see my language?
New languages are added by us. If you’d like us to add your language,
please contact us.
How quickly will my correction be released?
How quickly will my correction be released?
Corrections are released once the pull request is reviewed and merged,
usually within a few days.