Localisation feedback

[joshhunt]

In Grafana 9.3 we have added 4 new languages to Grafana: Spanish, French, German and Simplified Chinese.

With millions of users across the globe, Grafana has a global footprint. In order to make it accessible to a wider audience, we have taken the first steps in localizing key workflows. You can now set Grafana’s language for the navigation, viewing dashboards, and a handful of settings.

It would be great to get feedback on what areas of Grafana are important for you for us to work on translating and localising next.

As for supported languages, Grafana will be handling the translations with our translation partners, so we are not yet accepting contributions for translations. This is something we would like to accept, through a platform such as Crowdin, in the future, but we have no immediate plans for it.

For any issues with existing translations, please raise an Issue to this repository so we can triage and investigate appropriately.

[DmitrySidorow]

Russian language please

[kajla]

Hungarian language please.
We have a professional translation team.

[danmx]

Polish would be good too

[krzd7]

Can we have brazilian portuguese (pt-BR) added?

[TaylorHo]

I am ready if Grafana's Team need someone to carry out the translations. I can open a PR for that.

[4lenz1]

Japanese language please

[profijoeln]

Finnish language support would be greatly appreciated!

[krzd7]

Please, localise user related emails such as user password reset as per #60027

[igiornotigi]

I hope the Italian language will also be included! 🍝 ❤

[krzd7]

Hello @joshhunt ,

Any ETA on supporting new languages?

[yosiasz]

is the plan to use something like the following (i18)?

https://locize.com/blog/react-i18next/

[Mateorid]

Localization for plugins please. There is currently no way to translate them dynamically.
And for dashboard variables.
Add a global variable for the selected language so it can be used in payloads.

[btbf]

japanese please

[jensb]

I find that l10n is actually more important than i18n. Date formats in legends, comma vs. dot for decimals, all these can be much more misleading than some vocabulary that users need to learn. "3/10" can be March 10, or October 3, or 0.3, or "0,3", depending on where you are.

I did not try 9.3 yet, but I would prioritize localized date and number formats for tables, labels and legends much higher than trying to i18n every string in the app. (Also, a better mobile UX, but that's a different topic.)

[ahmetcanterlikci]

Turkish would be great! I'd also like to help

[Exudius]

Hello,
We can help translate for Italian langauge, we really enjoy your platform and our team has been using it these past months.

[dg-hasimoto]

Japanese language please.
If you don't have a Japanese translation team, we can help translate for japanese language !

[parumsancto]

ukrainian please

[alerts-ua]

I would greatly appreciate support for the Ukrainian language!

[baur]

Is there a release roadmap with new languages? or future plans with internationalization?

[austy81]

Czech language would be highly appreciated. Thanks

[natellium]

Hello! We want to let you all know that we are moving to Github Issues for feature requests and forum posts. You can read more about the move here.

This discussion was converted into a forum post, which is available here