A user reports that translations are missing after upgrading to Discourse 2.9.0.beta14, noting that the issue stems from a commit removing translations for multiple languages. The user highlights untranslated strings on the admin page, including messages about the notification menu and sidebar updates. gerhard explains that such issues occur when English strings change or new strings are added, requiring translators to update translations. Moin elaborates that translations must be updated when text changes, such as when feature modifications alter wording, and encourages users to help by translating on translate.discourse.org. C_T appreciates the explanation and acknowledges the need for updates.
Hello, I upgraded to 2.9.0.beta14( fa8d6860b1 ) recently.
I saw an English message on the above of my page:
Let’s start the discussion! There are 20708 posts. Visitors need more to read and reply to – we recommend at least 1000000 posts. Only staff can see this message.
We’ve updated our notification menu with improved filters to quickly see what notifications you have, and sort unread notifications at the top so you don’t miss anything.
That happens whenever we make changes to English strings or add new strings. It takes some time until translators provide new translations. You can speed things up by heading over to https://translate.discourse.org and translating the untranslated strings yourself.
If a discourse feature changes the texts sometimes change. For example here was mentioned, that since you can now choose groups that are allowed to use whispers, the text telling this post is a private whisper only visible to moderators is not correct anymore. Then the new wording needs to be translated again. After the wording changed the translation must be changed too.