GitHub user dosubot[bot] added a comment to the discussion: superset 5.0.0 translation display is incomplete
<!-- Answer --> The incomplete translation in the Charts area is likely due to two main reasons in Superset 5.0.0: 1. Starting with 5.0.0, translations (including frontend `messages.json` files) are not included by default in the Docker image. You must build your image with `BUILD_TRANSLATIONS=true` for translations to work—even if your translation files are up to date. If this step is skipped, translations will be missing or incomplete in the UI, especially in chart plugins. This is an intentional change to reduce image size and build time, not a bug. See [this explanation](https://github.com/apache/superset/issues/34428). 2. Recent changes (see [PR #34299](https://github.com/apache/superset/pull/34299)) refactored chart plugins to use a centralized translation function (`t` from `@superset-ui/core`) and rely on the global language pack loaded at startup. If the translation keys used in chart plugins are missing from your generated `messages.json`, those UI elements will not be translated—even if other modules are fine. Chart plugins are more susceptible to missing translations because their keys may not be included in the main extraction pipeline. To resolve this, make sure: - You build your Docker image with `BUILD_TRANSLATIONS=true`. - All chart-related translation keys are present in your `messages.po` and are correctly extracted into the generated `messages.json` file. - You rebuild frontend translations using the correct scripts, and confirm the Docker image includes the updated `messages.json` files. If you still see untranslated elements, check the browser console for i18n-related errors or missing key warnings, and verify that the untranslated strings are actually present in your language pack. Some UI elements may remain untranslated if their keys are missing or hardcoded, which is a known limitation and not considered a bug—contributions to translations are always welcome. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/77d27751-d28d-4d69-a489-0b190d97ed64?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/77d27751-d28d-4d69-a489-0b190d97ed64?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/77d27751-d28d-4d69-a489-0b190d97ed64?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/77d27751-d28d-4d69-a489-0b190d97ed64?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/77d27751-d28d-4d69-a489-0b190d97ed64?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/77d27751-d28d-4d69-a489-0b190d97ed64?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/77d27751-d28d-4d69-a489-0b190d97ed64?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34540) GitHub link: https://github.com/apache/superset/discussions/34540#discussioncomment-13994711 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
