Comment 1 for bug 350989

I don't if they are any legitimate updates to translated strings in the problematic bzr revision, nor whether any other commits had similar issues. If it's the only commit with this issue and if no existing string was intended to be changed in this commit (but the only intent was to translate missing/empty strings), then I recommend reverting the changes to existing strings in that commit.

Otherwise, we could either try to double UTF-8 decode all strings and keep the last version which decodes as UTF-8; we face the risk that some UTF-8 string encodes as valid UTF-8.