The translated revision history's have the Translated Content as well as the default Revision History content. Try building 13875 in Japanese as an example.
This was a bit hard to find, as I couldn't replicate it originally. Anyways the problem occurs when the Translated Revision History, has fuzzy or incomplete translations. It does this because atm the csprocessor will check to see if the topic has any errors, or warnings against the Topic and if it does, then it uses the current template and adds a <revision> or <revhistory> block, depending what can be found.
Fixed in 0.33.0
0.33.0 has now been released.