The Discourse team has temporarily disabled crowdsourced translations for several languages—including Arabic, Chinese Simplified, Dutch, Finnish, French, German, Italian, Japanese, Portuguese (Brazilian), Russian, Spanish, and Turkish—while a translation agency works on improving core and plugin translations for quality and consistency. Three new languages (Dutch, Russian, Turkish) were added to this effort. Users can still suggest translations via Crowdin, and feedback on agency translations can be submitted via #dev:translations or directly on Crowdin. A critical bug in Brazilian Portuguese (incorrect password recovery link) was reported by renato and fixed in pull request #19401. Although some users noticed translations still appear disabled on Crowdin spinodal, gerhard confirmed work is ongoing for roughly one more month. However, following a follow-up question from GuidoD, gerhard announced that crowdsourcing has now been re-enabled for core and all plugins, except for some pending Russian translations. Contributors may still receive email notifications for new strings, which can cause confusion about the status of the translation freeze.
Our translation agency is working on core and plugins again. We’ve disabled translations for the following languages while that’s in progress.
Arabic
Chinese Simplified
Dutch
Finnish
French
German
Italian
Japanese
Portuguese (Brazilian)
Russian
Spanish
Turkish
We are doing this in order to increase the quality and consistency of translations.
FAQ
Will you re-enable crowdsourcing for all languages?
Yes, we will re-enable translation for all languages after the translation agency finishes their work. We might disable it again shortly before or after each release of a stable version.
I still want to contribute translations. What can I do?
You can still suggest new translations on Crowdin. Our proofreaders will have a look at them.
I’m not happy with some of the new translations done by the translation agency. What can I do?
We value your feedback. Please create a topic in #dev:translations and explain your complaint with as many examples as possible. We will forward your feedback to the translation agency.
You can also post comments and issues directly on Crowdin and mention the translator or proofreader.
Heads-up: Our translation agency is working on core and plugins again. We’ve disabled translations for some languages (see above) while that’s in progress.
We’ve added 3 new languages that weren’t part of previous translation efforts:
I know we’re on proofreading so Brazilian Portuguese isn’t available for contributing as of now, but I just wanted to let you know that we have a critical issue with the current pt_BR translation: the password recovery flow doesn’t work at all, because it’s using a /session/email-login link instead of the correct /u/password-reset one.
The work is still ongoing. We will keep it that way for roughly one more month. I can’t promise anything, but I’ll see if we can make changes in the future to allow crowdsourcing while the translation agency is working on translations.
Thank you for the update. I forgot why I asked the question. We (contributors) are still getting emails for the changed/added translations. That’s why, every time I got the email, I think the work is finished.
Gerhard is there already a date when translation for us will be enabled again?
I just checked it for the new strings and at least German is still deactivated.
That’s a very good question. With the exception of some Russian translations, everything seems to be done. I’ve re-enabled Crowdsourcing for Discourse core and all plugins.
