translation file has not taken effect and the chart data is missing in the local language #34588
Replies: 2 comments
-
|
For the table chart time comparison columns: only the "Main" (or "SUM(Metrics)") column label is localized via translation files; the other columns (#, △, %) use hardcoded symbols and cannot be globally customized through translation files. However, you can set custom names for these columns individually in the chart's "Customize columns" (column_config) UI, including hiding the symbol by setting The issue where the "Main"/"SUM(Metrics)" column shows blank data in non-English languages is a bug: the frontend generates data keys using the translated label (e.g., "主 "), but the backend always sends data with keys like "Main ". This mismatch causes the data to disappear when the UI language is not English [source]. For translation effectiveness: starting with Superset 5.0.0, Docker images must be built with If you need to avoid the symbols or want more control, use the per-column customization in the chart UI. For the missing data bug, the only workaround is to use English or avoid time comparison columns until the frontend-backend key contract is fixed. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
|
Часть полей в superset:6.0.0 остаётся на EN, при переключении на любой язык, хотя переводы в po/mo/json присутствуют. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone! Recently, I tried to deploy Superset as a data analysis tool. When adding a chart (of table type) and using time comparison for comparative analysis, the table automatically generates four columns: SUM(Metrics), #, %, and (empty). Here's my question: SUM(Metrics) allows custom column names. Can the #, △, %, and columns also have their names customized to avoid displaying symbols (#, △,% )?
Another issue I'm currently struggling with, which might be a bug, relates to the effectiveness of translation files. The master source code has very incomplete Chinese localization. I've tried modifying most translations locally by converting messages.pot to po files. I built a Docker image using the latest master source code's Dockerfile with BUILD_TRANSLATIONS="true" added. The messages.mo and messages.json files were successfully compiled in the image. However, after running the container, the login page translations didn't take effect even when selecting the local language. In the chart editing interface, most content still doesn't show translated content, such as Query mode, Dimensions, Filters (though translations work when clicking to set content), Time Comparison, and condition list content. If I select line chart, some content is translated (X-axis, X-Axis Sort By). I checked the messages.po and messages.json files, and terms like Query mode, Dimensions, Filters, and Time Comparison all have translation content. This is just an example, many other charts have the same issue.
However, when I import the same translation files ( messages.mo , messages.json ) using the apache/superset:5.0.0 image from Docker Hub, the above interface translations work correctly:
But there's another problem: when adding a chart (of table type) and using time comparison for analysis, the table automatically generates four columns: Main, #, △, %,. In the new version, SUM(Metrics) has replaced Main. It seems Main would extract translation results from the translation file, but this causes the entire column of data to be missing. If I switch back to English, it displays normally.

Thanks to anyone who helped! Thanks a lot!
Beta Was this translation helpful? Give feedback.
All reactions