Users reported that titles and tooltips on graphs in the community health dashboard weren’t localized, despite other parts of the interface being translated. schneeland provided screenshots showing the issue, and tvavrda confirmed it persists, referencing a related thread. sam flagged it with the team and invited contributions. martin submitted PRs to fix the report titles and tooltips, noting missing Czech translations for “In Reply To” — which tvavrda later confirmed were newly translated but not yet committed. tvavrda also identified untranslated tooltips, pointing to the relevant code; martin agreed to fix it. Further PRs addressed additional missing translations, including time period labels martin. tvavrda asked whether to update related topics; schneeland noted remaining untranslated elements like the back link and site recommendation text. Moin clarified these are new strings awaiting translation merge (typically every Tuesday) and can be verified using verbose localization.
As the title already says: it seems that the strings for the titles on graphs in the community health dashboard are not localized:
When switching to the reports tab, the localized titles are shown:
However, when looking at an individual report/graph, again the English title is used and both day and count in the table headings are also not localized:
This is still the case. Also noted here: Report locale copies do not update with user locale.
Can it be fixed?
I have flagged this with the team, no timeline though on when we can resolve this.
Would you like to try out making PR to improve this?
It might be challenging for me 
And as we speak the notification mail I’ve got has not the In Reply To heading localized, although the e-mail otherwise seems to be translated.
This should fix the report issue:
https://github.com/discourse/discourse/pull/30524
For the “In Reply To” issue, it looks like our Czech translations are a bit lacking, our German server.de.yml file has user_notifications.in_reply_to but server.cs.yml does not. Translations fall back to English when keys are missing.
I am sorry, you are right. I confused myself. I translated the phrase just 4 days ago and yesterday it looked like it should have worked. The translations have not been committed yet though.
Thanks for the fix, it works!!
I noticed the tooltips are not translated.
Found the piece of code as well:
I am just a c# guy, so I am not able to make PR’s. 
Come on, C# is close enough to Javascript! 
Thanks for finding that, I will make a PR to fix the JS to use I18n.
This will fix the other issue, though you won’t see any practical change until our next round of translations:
It’s not all. I commented on the PR although it was merged, not sure if you can spot it.
There are more translations below (“two weeks ago” and “in the previous 30 day period”).
This next PR should fix those issues, as well as the comments Gerhard added!
There seem to be other topics referring to the same problem. I don’t want to bump them all. What is the right thing to do? Just let them be or should they be somehow updated or closed?
First of all: thanks a lot! I didn’t have enough time to comment in the meantime, but I see that localization is applied much more widely in the dashboard now.
On small thing I still noticed: the back link to the report overview page does not seem to be localized.
And recommendations regarding site settings appear in English, too:
They are. You can see that when you enable “verbose localization” because they have a number.
Those are just new strings, both were translated to German 4 days ago, but translations are only merged once a week. So brand new strings, that were added after translations were merged (or slightly before and no one had time to translate them in time) fall back to English. The translation will be added the next time translations are merged (usually Tuesday) and you will see them after updating.
