2 rewind strings are reappearing for translation without being changed on GitHub after each release

My impression is that something in the new lifecycle of strings on Crowdin is not working as expected for js.discourse_rewind.cannot_view_rewind_gibberish and js.discourse_rewind.cannot_view_rewind.

Based on the git blame, these were only changed in December.

But it feels like they reappear for translation with every release. It’s a little difficult for me to confirm because I cannot see deleted texts.

But I can see that while the text wasn’t updated, I have now added a comment about the text not needing a translation three times. Each time because it reappeared for translation.



And I can see that in both cases it reappeared, this matches with a new release.

Maybe there is a problem with the quite high number of special characters/formatting that causes this? There was a slight change once on Crowdin while nothing changed on GitHub, but the latest version seems to be identical, so Translation Memory handled it, but this still needs to be approved again, which seems unnecessary to me. And those who hadn’t translated the prior version now have to translate both separately.

1 Like

There was an issue during the release rollover that caused some files to get out of sync between the release and latest branches. discourse-rewind contained one of the affected files.

The fix I applied in response to Why were that many translations removed? - #9 by gerhard should address this here as well.

Please let me know if you notice this happening again after the next release. It shouldn’t.

2 Likes