Translate and customize your Space with text overrides
Language | Code |
---|---|
German | de |
English | en |
English - Great Britain | en-GB |
English - Canadian | en-CA |
English - South African | en-ZA |
Spanish | es |
Spanish - Latin America | es-419 |
French | fr |
French - Canadian | fr-CA |
French - France | fr-FR |
Indonesian | id |
Italian | it |
Japanese | jp |
Korean | kr |
Malay | ms |
Dutch | nl |
Polish | pl |
Portuguese | pt |
Portuguese - Brazilian | pt-BR |
Swedish | sv |
Thai | th |
Turkish | tr |
Vietnamese | vi |
Chinese - Simplified | zh |
Chinese - Traditional | zh-Hant |
Chinese - Hong Kong | zh-Hant-HK |
languageOverride
property. This property can be set either directly on the Space or at the environment level if the Space has not yet been created.
All users who use the Space will only see the language set in the language override property. Browser settings will no longer be respected.
To specify the language, simply assign the appropriate language code (e.g., ‘en’ for English, ‘fr’ for French, etc.) to the languageOverride property.
/locales/en/translation.json
.
Don’t have an english file? You can use any other language instead.
Your translationsPath
must meet a few requirements to work as expected:
yourCustomTranslationsDirectory
can be swapped out for any path desired.translation.json
file, the system will display the key itself as a fallback. Therefore, it’s encouraged to always have a default language translation available to avoid showing raw keys to the users.
key1.key2
) to organize translations effectively and maintain readability.translation.json
file to ensure it follows the correct JSON format to prevent errors during runtime.