Bug description
as show in the image, the translation is loaded correctly, but the browser display english not chinese.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.11
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
Partial translation in Superset usually happens when some translation keys are missing or outdated in the Chinese translation files. This is especially likely after recent changes—like the August 2025 update that enforced sentence case in button text and changed keys such as "Create Chart" to "Create chart". If your translation files (e.g., superset/translations/zh/LC_MESSAGES/messages.po) don't match these new keys exactly (including case), those UI elements will stay in English see details.
To fix this, make sure your translation files are up to date and complete. Check for any empty or "fuzzy" translations in your .po files, as these will also cause fallback to English example. After updating translations, always rebuild the frontend translations with npm run build-translation (and set BUILD_TRANSLATIONS=true if you use Docker) reference.
Also, make sure the locale code is consistent between your browser, backend, and frontend (e.g., all using zh or zh_TW). Locale mismatches can cause some parts of the UI to remain untranslated see workaround.
If you follow these steps and still see issues, check your browser console and Superset logs for i18n-related errors.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: msyavuz
Thanks for reporting this, created a pr to fix it.
Comment From: lx1054331851
@msyavuz I noticed that all third party chart plugins translation all not applied. messages.mo and messages.json are all correct.
Comment From: msyavuz
@lx1054331851 If you are talking about the chart descriptions, the linked pr should fix them, if not can you specify which translations?
Comment From: imedlee
@msyavuz The translation of the charts in version 5.0.0 is complete. However, after version 5.0.0, there is a lot of missing translation in the chart part, including chart tags, categories, the control panel for chart visualization, etc. It is also unclear which changes have caused this issue.
Comment From: msyavuz
I looked into this a bit more and i think there is a race condition between language packs loading and translations, i will try to include a fix in the linked pr
Comment From: rusackas
@mistercrunch I think you made some changes around the language pack loading... do you have any theories here?