Screenshot
https://github.com/user-attachments/assets/7ae05fba-99d3-4ed5-88c9-0e15778550e1
Description
In Superset 6.0.0, partial UI elements (such as button labels, visualization panels, and tooltip texts) are not being translated to the target language as expected. This issue persists across all non-English languages (tested with Chinese, French, Spanish) despite:
- Docker image built from the 6.0 branch source code with ARG BUILD_TRANSLATIONS="true"
- Correct language configuration in superset_config.py
- Full reload of the application
Specifically Affected Elements: 1. Visualization panels: Chart configuration controls and settings panels show mixed translations 2. Tooltip texts: Hover tooltips in chart building interface display untranslated English text
Reproduction Steps:
1. Set target language in superset_config.py:
BABEL_DEFAULT_LOCALE = "zh"
LANGUAGES = {
"zh": {"flag": "cn", "name": "简体中文"},
"en": {"flag": "us", "name": "English"},
"es": {"flag": "es", "name": "Spanish"},
"it": {"flag": "it", "name": "Italian"},
"fr": {"flag": "fr", "name": "French"},
"zh_TW": {"flag": "tw", "name": "Traditional Chinese"},
"ja": {"flag": "jp", "name": "Japanese"},
"de": {"flag": "de", "name": "German"},
"pl": {"flag": "pl", "name": "Polish"},
"pt": {"flag": "pt", "name": "Portuguese"},
"pt_BR": {"flag": "br", "name": "Brazilian Portuguese"},
"ru": {"flag": "ru", "name": "Russian"},
"ko": {"flag": "kr", "name": "Korean"},
"sk": {"flag": "sk", "name": "Slovak"},
"sl": {"flag": "si", "name": "Slovenian"},
"nl": {"flag": "nl", "name": "Dutch"},
"uk": {"flag": "uk", "name": "Ukranian"},
}
2.Navigate to Charts functionality
3.Observe mixed language presentation (partial EN, partial target language)
Comment From: dosubot[bot]
Partial translations in Superset charts and tooltips are usually caused by incomplete entries in the translation files for your target language (like messages.po in superset/translations/zh/LC_MESSAGES/). Recent updates in Superset 6.0.0 changed many UI strings and translation keys, but not all translations for non-English languages are fully up to date, which leads to mixed-language UI in chart panels and tooltips. You can confirm this by checking for empty or missing translations in your .po files—many chart and tooltip strings are present but untranslated in Chinese, French, and Spanish files, especially for newer or updated UI elements source.
To resolve this, update and complete your target language's messages.po file using pybabel, then rebuild frontend translation assets with npm run build-translation in the superset-frontend directory. Also, ensure your locale codes match between frontend and backend, and consider adding a bootstrap locale override in superset_config.py if you use variants like zh_TW or pt source.
Recent PRs show active maintenance of translation files, but some lag is expected for new strings. If you want to contribute missing translations, follow the Superset translation workflow with pybabel and submit updates upstream source.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: sadpandajoe
I think these are just missing translations unless if you were seeing these in 5.0 or earlier. @imedlee is that the case?
Comment From: imedlee
I think these are just missing translations unless if you were seeing these in 5.0 or earlier. @imedlee is that the case?
The version I'm currently using is a Docker image built from the source code of the 5.0 branch, my own messages.po file 34597, and with the ARG BUILD_TRANSLATIONS="true" setting, and its translations display correctly. Also I import the same translation files ( messages.mo , messages.json ) using the Docker image apache/superset:5.0.0, the above interface translations work correctly.34588
In version 6.0, I also use the same messages.po file, while other languages use those from the source code.
Comment From: rusackas
In version 6.0, I also use the same messages.po file, while other languages use those from the source code.
I might be misunderstanding... but does that mean you're using the 5.0 translation files in the 6.0 release? I could foresee a LOT of missing things, if that's the case.