I don’t think this is currently a priority.
The open-source n8n project already has a reserved setting for multiple languages. You can refer to this open-source project: GitHub - other-blowsnow/n8n-i18n-chinese: n8n 配置多语言 to configure it. It’s very simple, especially if you are familiar with Docker.
I think expanding language support would be a really valuable improvement, especially for adoption in regions where English becomes a barrier for non-technical users. Chinese seems like a strong candidate because a lot of automation users are already creating community translations and localized resources around n8n. The editor already has internationalization support and self-hosted users can configure locales through N8N_DEFAULT_LOCALE, but official UI localization and an in-product language switch would make onboarding much easier.
Even if full translation isn’t a short-term priority, starting with community language packs and allowing users to switch languages from settings could be a good middle step. There are already community efforts for Chinese localization, which suggests real demand exists.