Hi there!
We recently started localization process. As result we do many iterations on source text to shorten or lengthen it. However when we gather text again, put new translations and compile to test in Standalone mode it does not show up.
The game just uses Source text and forgets about Translated text.
Also we tried to regenerate key for Source text and set new namespace - it does not work. Is there a way to clean localization somehow?
Localization dashboard shows changed Source text so we always translate it and compile. Then nothing happens in Standalone game mode. Is there solution to this problem?
P.S. We have working in-game menu to choose language. So problem is not there really…
1 Put your Localization target files into Content/Localization/{Target Name}
2 Put InternationalizationPreset=All and +CulturesToStage={lang code here - the same as a folder name} to ProjectPackagingSettings in DefaultGame.ini
3 Add relative path to your Target folder in DefaultGame.ini and DefaultEngine.ini (it is in both files - not sure which one is used)
And don’t forget to compile)
That works fine in 4.18 - not sure about 4.17, but could be worth trying
Yes! Yes! Yes!
I have set correct Cultures and Internationalization values since many other Source text values are correctly translated.
Problem is related to Source text that was changed and needed to be translated again.
If you see translations for the changed source when you export your PO files, then your translation is there and working. If you see an empty translation, then it isn’t.
Changing the source invalidates its translations, but the translation editor doesn’t show this properly as prior to 4.19 it didn’t understand “stale” translations, and was only checking whether a translation existed for that identity (namespace + key), and not that the translation source also matched the current native text (as the PO export and compile step do). You can skip this source check when compiling by enabling the “Skip Source Check” option for your localisation target.
If you’re working with a packaged game, you must re-package the game after changing your LocRes files (to get the updated LocRes files into the package). If you’re running a cooked game, or the editor in -game mode, you don’t have to do this. 4.18+ makes it easier to test localisation as there’s now an in-editor preview that works with PIE/UMG/etc.
If you’re still having issues with this, zip up your Content/Localization folder and send me a link to it on the forums PM. I can take a look at them and see what sort of state you’re in.
Have you added the correct cultures to your list of cultures to stage (under the Packaging section of your project settings?). You also need your “Internationalization Support” set to something other than “English” (use “All” if you’re unsure).
From taking a look at the data I was sent and talking to you via PM, it seems you have a stable keying issue that’s affecting a few of your texts and causing some translations to be ignored.
The problem texts happen to reside within a User Construction Script, and I do recall some issues with stable keys and UCS.
For now I would advise moving those texts elsewhere (like a String Table) and I’ll investigate the UCS issue later (I may have fixed it already).
