Sometimes when new features are added existing, text is edited. The issue is that only the English text is updated, while translations remain outdated until the next scheduled merge from Crowdin, which usually happens on Tuesdays.
This creates a delay: if a feature is merged on Wednesday, and someone updates their forum shortly after, they will see the new feature but not the updated texts - unless their interface is in English. This mismatch can be quite confusing.
A recent example are the themeable site settings which were merged on a Wednesday. In that case the description of the themes page was extended and “Theme settings” was changed to “Custom theme settings”. In English, this change helps users find the new location where these settings are configured. But in German, I don’t see that.
I have to wait for the Crowdin translation update - and then it also depends on when my site is updated. So it takes even longer before I get the updated text.
In this specific case, it’s “just” some guidance that’s missing. But there are other times where the meaning of the text changes completely, or the placeholders are changed, and things can even look broken.
Would it be possible to remove outdated translations in the feature’s pull request when a text string is modified? That way, users would fall back to the updated English version instead of seeing an outdated or misleading translation.
I think in most cases, a current English string is more helpful than an outdated translation in my preferred language.
