We recently partnered with a company to translate their upcoming game. Roblox failed to auto-capture FTUE dialogue, so we manually added the strings to the portal. Now that everything is translated, Roblox will still not find the location of the strigns & we cannot see the translated version of the string in-game, even though the exact text is translated in the Roblox’s localization portal.
Expected behavior
What we expected to happen is for Roblox to replace the text-label (original text-string) with the translated version of the string, even though the machine failed to capture the strings itself.
Hey George, can you try removing the context field "FTUE Window’? As explained in the docs, the ‘Context’ field is the exact path to the in-experience object containing the string.
“Example” is the field where you can input details like “FTUE Window”. If that still doesn’t work, let us know.
Correct me if I am wrong, so as not to add everything manually we downloaded the CSV localization file and we edited the context out, and re-uploaded it replacing the old cloud table with the new one. That should work right? Asking because we haven’t seen any changes yet!
Hey George, I believe we sent a bunch of questions about this issue via devrel. One of the turtles mentioned that this was a confidential release, so not sure how much you can share here (e.g. game ID, the setup of the translations, which translations are working vs not working, how you set up / render the strings for which the translations aren’t working). Happy to keep chatting here if this is information you can share.
ETA: Alternatively you can see if the dev is open to adding our usernames to the game to see what’s going on.
Just confirming that the issue is resolved, and it was because the dev accidentally turned off ATC for those labels. If everything is good, we’ll close out the ticket
