\o/ Congratz on localizing your game.
Let me explain how the system is intended to work.
Currently, the editor never loads game specific localization files. This is important because otherwise you could accidentally get into a state where translations are saved over your source text. Thus instead you need to run your game in stand-alone mode. You can do this through the Play menu in the editor or from the editor startup command line by passing -game. Under the advanced options for the Play menu you can specify command line parameters, so if you’d like to launch into a specific language you can do that by specifying “-culture=en” on that command line.
Obviously a packaged build will always attempt to load game specific loc.
By default the engine will attempt to find localization data that is appropriate for the OS’s desired locale/culture. This should work on all platforms, including mobile. Let us know if this is an issue.
You can hot swap your culture in-game by using the in-game command prompt (open with ctrl+shift+~) and typing “CULTURE=en”.
The engine only has one current culture, thus calling SetCurrentCulture while in the editor will cause it to load different localization data as well.
If calling SetCurrentCulture is causing your game loc to load in the editor you may have configured your game localization targets incorrectly. You should have at least one Game specific loc target separate from the existing Engine and Editor ones. We normally push to have it called ‘Game’ by default.