Auto Localization ambiguous text can be over-aggressive

Bug Reports Other Bugs
,
1

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:
image
the timer actually ended .024, but the translation string accidentally reuses {number1} at the end, causing this weird behaviour

image
image201×105 21.3 KB

from the test game linked

2

Is there any news on this issue? We fixed the broken translation entry in our game about a year ago, but this issue has recently revived itself from the dead somehow despite the translation entry being fine in the csv
"{player1} placed #{number1}/{number2} in the style {style} with a time of {time1}.{number3}" (number3 used to be number1, which is how this bug was originally found, but that was fixed a long time ago, and hasn’t changed, nor has a new broken entry appeared afaict)
image