khashashin commented on issue #32854: URL: https://github.com/apache/superset/issues/32854#issuecomment-3419840366
Very unfortunate this discussion didn’t continue, it looks like metadata i18n is no longer being actively pursued, which is a real shame for multi-language deployments. I really like the TRANSLATION_HOOK approach mentioned above: > From a deep conversation with PMCs today - there seemed to be traction for a simpler solution around a more generic "translation hook", where administrators would be free to implement a generic function to hook up with an external translation service. The high level idea is that you would have some sort of TRANSLATION_HOOK(text_to_be_translated, context_object) function defined in something like superset_config.py and externalize the translation process through that. That hook would assume the external service is in charge of accumulating strings to be translated, memoization, and serving the text -> do whatever makes sense to you in there. That abstraction is exactly the kind of lightweight, pluggable interface that would let Superset remain minimal while enabling many deployment-specific workflows. In my case I need per-dashboard / per-chart multitenancy: each dashboard belongs to a tenant and the translation platform for each tenant is different. The `context_object` idea maps perfectly to that, the hook can receive tenant/dashboard identifiers and route to the correct external source. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
