Recently I noticed that some strings in Transifex have lost their translations. E.g. this one:

You've earned the "$badgeName$" badge ($badgeDescription$) for "$postTitle$".

I know that the same string was already translated and used on ruSO for a long time. Now translation is lost, but even Transifex says that there is a 100% match string in suggestions (acquired from the translation history). This means that the new string is the same as the old one and should not be reset as happens if the original string is slightly modified (even with one symbol).


Why did this happen? Did you change the string's key generation (hash) function? Could this be prevented in future updates to minimize losing of translations?

  • Might be Transifex bug, time to add a tag for this. :) Jan 23, 2018 at 9:15
  • @ShadowtheHedgehogWizard whoa new tag! Need to retag many of my old questions! Jan 23, 2018 at 9:18
  • Hold your horses... give it a day or so, other high rep user might disagree with me and remove the tag, in which case better start discussion if we need the tag or not. With all due self respect, I do mistakes sometimes, and don't want to do big changes on my own. If the tag "pass", then we can safely start retagging other questions. :) Jan 23, 2018 at 9:20

1 Answer 1


On February 7th fixes went out to address this "flaky localization strings" issue.

The main issue for the flaky strings was an unstable ordering of the variant parameters which caused the trailing part of the string id (after the hash, countA=one,countB=many) to differ between builds.

The parameters are now sorted in the order of appearance, which is a sort that affected the least strings.

Strings with following hashes were affected:


Additionaly some strings that were flaky, did loose their translation on Transifex, but they still remain localized in our canonical DB, and on the website.

  • 1
    But the string that mentioned in the question doesn't have variant parameters. Feb 19, 2018 at 12:58
  • Thank you @m0sa for fixing this bug! I wonder, is there any way to get a list of the additional "flaky strings"?.. I understand those strings are correct on the database and will render just fine on the site. However, all variants are picking only one of the translations as suggestion, which may lead a reviewer to approve the wrong variant, hence overwriting the string in the database
    – Mariano
    Feb 19, 2018 at 16:26
  • we could coordinate a freeze (because it would override all unreviewed changes) and push to get everything (translated strings) from our canonical DB up on Transifex (we only push "new" English strings during our regular builds)
    – m0sa
    Feb 19, 2018 at 17:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .