How to change the Superset-UI page language to Chinese? I added the following configuration, but only some data is translated.

[MMM-Source]

How to change the Superset-UI page language to Chinese? I added the following configuration, but only some data is translated.
BABEL_DEFAULT_LOCALE='zh'
BABEL_DEFAULT_FOLDER = 'superset/translations'
LANGUAGES = {
'zh': {'flag': 'cn', 'name': '简体中文'},
'en': {'flag': 'us', 'name': 'English'}
}

[dosubot[bot]]

Hi @MMM-Source! I'm Dosu and I'm helping the Apache Superset team.

Your configuration looks correct, but partial translation is expected behavior — Superset's Chinese translation coverage is incomplete by design since it's community-maintained [1]. That said, there are a couple of things you can check to maximize what is translated:

Ensure both backend and frontend translations are compiled. Superset uses two separate translation pipelines [2]:

1. Backend (Flask-Babel .po → .mo):

   pybabel compile -d superset/translations

2. Frontend (.po → .json):

   npm run build-translation

If only the backend translations are compiled, the frontend UI strings will remain in English (and vice versa) [3].

If you're using Docker, you can enable translation compilation during the build:

BUILD_TRANSLATIONS=true docker compose up

[4]

Other tips:

• Make sure you're using 'zh' consistently as the locale key — mismatches between zh, zh_CN, and zh_TW can cause lookup failures [5].
• The zh translation file has ~14,600 entries [6], but not all strings are translated. Untranslated strings will fall back to English.

Unfortunately, incomplete translation for non-English languages is a known limitation that Superset acknowledges — i18n is actually disabled by default for this reason [7]. Contributing translations via the .po files is the way to improve coverage over time.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.