Turkish (tr) localization - is n8n ready to accept community translations yet?

Feature Requests
1

Hi n8n team,

I’d like to contribute a complete Turkish (tr) localization for the editor UI — but per CONTRIBUTING.md (“ask before you start”) I want to confirm the policy before writing a single line.

Why I’m asking instead of opening a PR: the answer has been “not yet” twice already, and I’d rather not add a fourth closed translation PR.

  • Jun 2024 — @bartv: “Thanks for the offer! We’re not supporting multi-language yet - maybe in the future” (topic)
  • Jul 2025 — @Joffcom, closing the Korean PR (#17018): “We are not currently accepting translations so I am going to mark this as closed but as soon as we are ready I will let you know.”

Since then the Japanese PR (#21208) sat for 6 months and was auto-closed by the stale bot, and packages/frontend/@n8n/i18n/src/locales/ still ships only en.json.

What I’m offering: a native-quality Turkish translation of all 8,319 keys (~42,800 words) in en.json, plus a commitment to keep it in sync across releases rather than dropping a one-off dump.

My questions:

  1. Has the position changed — are community translations on the roadmap now, or is it still “not yet”?
  2. If yes: what workflow do you want? A single tr.json PR conflicts with the 1000-lines-per-PR rule (en.json is 8,350 lines). Should it be split across many PRs, or are you planning a translation platform (Crowdin / Weblate) instead?
  3. If it’s still “not yet”: is there an issue or milestone I can subscribe to, so I can time the work instead of guessing?

If upstream isn’t ready, I’ll publish and maintain it as a standalone language pack (N8N_DEFAULT_LOCALE=tr) — but I’d much rather it live upstream where every Turkish user gets it by default.

Thanks for the great project!