How to localize a language completely

[iceangel86868686-bot]

Hello everyone, please tell me how to translate the superset into Russian completely.
Here are my settings:

This is the file ~/venv/lib/python3.10/site-packages/superset/config.py

I also have .po .mo .json files ~/venv/lib/python3.10/site-packages/superset/translations/ru/LC_MESSAGES/

But I still have untranslated words.

I decided to check the presence and translation of the word "Metrics" in the .po and .json files. There is a translation there

Tell me, who knows what's going on?

[dosubot[bot]]

Hi @iceangel86868686-bot! I'm Dosu and I’m helping the superset team.

The issue you're running into is a common one — having translations in your .po and .json files doesn't automatically mean they'll show up in the UI. There are a few things to check:

1. Ensure both backend and frontend translations are compiled

Superset uses two separate translation pipelines [1]. Even if your .po file has the translation for "Metrics," you need to make sure both compilation steps have been run:

• Backend (.po → .mo):

  pybabel compile -d superset/translations

• Frontend (.po → .json):

  cd superset-frontend
  npm run build-translation

  (cite:docs:afdb9d10:549-568)

If you only updated the .po file but didn't recompile the .json, the frontend React components won't pick up those translations. Most of the UI labels you're seeing untranslated (like "Metrics") are rendered by the frontend, which reads from the .json file in JED format, not the .po file directly.

2. Frontend loads translations via server-rendered bootstrap data

The frontend doesn't load .json files separately at runtime. Instead, the backend embeds the language pack into the HTML page as bootstrap data (cite:code_file:48df91aa:130-141) (cite:code_file:135d84e8:37-43). This means after recompiling translations, you need to restart the Superset server for changes to take effect.

3. Some strings may have plugin-level type mismatches

A known issue is that some chart plugin controlPanel configurations use the translation function t() in a way that causes type mismatches, preventing translations from rendering (cite:thread:4d2fb152). For example, a label defined as label: t('Metrics') may not translate correctly if the component expects a function. The fix requires changing it to label: () => t('Metrics').

4. Incomplete translation coverage

By default, Superset actually disables i18n because most language translations are incomplete (cite:code_file:9bbde5f2:401-403). The Russian .po file may not have translations for every string in the application. You can check completeness by looking for empty msgstr entries in your .po file:

grep -c 'msgstr ""' superset/translations/ru/LC_MESSAGES/messages.po

Recommended steps:

1. Re-run pybabel compile -d superset/translations and npm run build-translation (from superset-frontend/)
2. Restart the Superset server
3. Clear your browser cache and reload
4. For any remaining untranslated strings, check the .po file to confirm the msgid matches exactly (case-sensitive, including any trailing spaces)

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[iceangel86868686-bot]

I have compiled for the Russian language
3 errors were found, I open the file, and I don't understand what he doesn't like. It also says that everything should work fine. Okay let's continue

One more question, there is no superset-frontend directory.
I installed it via pip

[dosubot[bot]]

Since you installed Superset via pip, the good news is that pre-compiled .mo and .json translation files should already be included in the pip package. The release process compiles both backend (.mo) and frontend (.json) translations before publishing to PyPI [1].

So if you check your ~/venv/lib/python3.10/site-packages/superset/translations/ru/LC_MESSAGES/, you should already have both messages.mo and messages.json — and from your original screenshots, it looks like you do.

About the 3 compilation errors: Those warnings from pybabel compile are usually about minor formatting issues in the .po file (like mismatched placeholders %s/%d, or encoding issues). If it says compilation otherwise succeeds, they typically don't block translations from working.

About the missing superset-frontend: You don't need it for a pip install. The frontend is pre-built and the .json translation files are already compiled and included. You don't need to run npm run build-translation.

If translations are still not appearing after all this, the most likely culprit is that the existing .json file in the pip package was compiled from an older or incomplete .po file. If you've manually edited your .po file to add translations, you'd need to regenerate the .json. You can do this without the full source checkout by installing po2json as a standalone npm tool [2]:

npm install -g po2json
po2json superset/translations/ru/LC_MESSAGES/messages.po superset/translations/ru/LC_MESSAGES/messages.json --domain superset --format jed1.x

Then restart Superset and clear your browser cache. The frontend reads translations from the .json file that's embedded into the page by the server at load time [3], so a restart is required after any changes.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[iceangel86868686-bot]

I started executing commands and errors started appearing

[bergstar]

Hello everyone, please tell me how to translate the superset into Russian completely. Here are my settings:

Hi! Could you please be so kind and share the Russian translations?