If you have a translation string such as {thing} is {thing}, the automatic localization can attempt to translate strings that simply match the ambiguity requirements of the string like “a is b”, even when the 2 occurances of {thing} don’t match. This can cause the original english text to be modified in unexpected and unclear ways as a result of a bad translation string
I’ve set up this behaviour in a test game, localization - Roblox, with the {thing} is {thing} translation set up. Try typing anything that goes “x is y” in the input box in the bottom left to see the behaviour
Some examples of the bug:
the timer actually ended .024, but the translation string accidentally reuses {number1} at the end, causing this weird behaviour
from the test game linked