Nexus Localizer - Runtime Language Changer

If Roblox adds run time localization, this should not be used because that implementation probably will involve using LocalizationService.RobloxLocaleId and proper changing of auto localizated text.

One of the problems I have with the current languages on Roblox is I have gotten offers and paid translators to do unsupported languages, like Russian, Latvian, Swedish, Finnish, and Korean. I have no way of testing them in-game to make everything looks good, and if the assets are showing up. Since no one else made a language changer, I decided to make my own.

How It Works
The biggest problem with making a language changer is LocalizationService.RobloxLocaleId read only. I could make my own localizer, but that would be hard because of the amount of logic required for regular expressions and picking what phrases to use. Not to mention the resource cost when changing languages. I discovered a pretty cool hack to get Roblox to change the localized language.

  1. Get the localization tables used (parented to LocalizationService and set by RootLocalizationTable.
  2. Divide all the entries of the tables as if they were separated tables.
  3. Set the translated languages to the LocalizationService.RobloxLocaleId. This even works when translated the same language, like en-us -> en-us. The tables can be re-parented to change the language, as well as changing the RootLocalizationTable.

Limitations
There are some limitations with this system. The limitations include:

  1. There is no out of the box core GUI localization.
  2. LocalizationService.RobloxLocaleId still doesn’t change. Scripts require using a value named “CurrentLanguage” value inside the script when run.
  3. It relies on the current setup of frames in the chat. Renaming the frames will result in it not working. It does work with FearMeIAmLag’s Emoji Suite, a fork of the chat system.
  4. The chat transparency isn’t directly linked to the localization list. I couldn’t figure out a way to get around it without forking the chat script.
  5. There may or may not be a few missing languages. I used a script to parse the list of languages that Microsoft supports, but only did 2 character and 5 character codes. (Please PM me or post in this case).
  6. Referencing LocalizationTable references may not work as intended because they change.
  7. Adding/removing entries at run time is not supported.
  8. Checking if the RootLocalizationTable matches a certain value (another table) will break.

Screenshots from Roblox Battle (2018 Edition)
Once I get other languages added, I will post more pictures to show it working for non-supported languages.
Spanish (played as English):

French (played as Spanish):

Portuguese (played as French):

Korean (played as English):

Swedish (played as English):

25 Likes

Very nice, I was looking for something like this for my next project. Is there any noticeable lag or delay with switching between languages on the fly?

Also the Emoji Chat Suite was made by me, I just implemented it into Flight :wink:

1 Like

I haven’t noticed any delay when changing languages in Roblox Battle (2018 Edition).

Whoops. Fixed that in the OP.

1 Like

LocalizationService is nothing but a lag-generator, would remove it permanently if I could.
Nice script tho!

1 Like

Have you reported a bug with your case? I haven’t had any problems with it, and it looks like people internationally that are playing aren’t having problems.

If you open dev console it will generate huge lagspikes at frequent intervalls. Checking the microprofiler shows it’s localizationservice doing useless infinity loops for no reason.

I have reported it and posted a suggestion to add a disable button, but all I’ve got is: You should just set AutoLocalize to false on all your gui objects.
Which works, unless you need devconsole to debug lag.