tvavrda
2025 年1 月 10 日 16:09
13
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?
Reports, along with their locale strings, are being cached in the server’s locale, such that users with a differing locale will see an incorrect locale on some reports - should Discourse also pass a localization string in reports so that reports are properly localized?
EG, this is a screenshot of a default EN site, with a sr user:
[Screen Shot 2019-12-13 at 11.37.29 AM]
Hello community [image]
I wanted to add translations to those strings in Crowdin but those strings already have translations. So I ran a search query and found out this topic:
It looks like there was a PR but was not merged at the end.
Was there any progress with that issue?
Thank you
I have found some strings that are translated in Transifex, but doesn’t appear translated in production. They are in Admin>Dashboard: Signups, Topics, Posts, Daily Engaged Users, New Contributors, Top Referred Topics, Trending Search Terms, Users per Type… (with its corresponding tooltips).
This issue is common to all languages. I have checked different locales (French, German, Catalan…), and the strings always appear untranslated.
2 个赞