Localization issue: only new content gets translated while older text remains untranslated. After several export/compile attempts the map lost all translations. Deleting the (LOCALIZATION) folder manually fixed it, but it seems unintended.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Other
Steps to Reproduce
Open a project in UEFN.
Export and compile localization.
In-game, some texts appear translated and others not.
Try exporting and compiling again.
In-game, no text is translated at all.
Expected Result
The map should be normally translated into all languages.
Observed Result
The map shows no translation at all, even though all text blocks are marked as translated.
This bug also happened to another creator I know, and the only solution we found was to delete the (LOCALIZATION) folder in the project files and then export and compile again. Was it supposed to work this way?
The texts on the map images should be translated into Portuguese, but they are not.
So just to confirm; you had translations in your .po files, but those translations didnât appear in game? If so, did they remain translated if you re-exported localization?
Do you know if you had the .ugcloc file in the root of your Content/Localization// folder when you were having this issue?
Does your .uplugin file have a âUGCLocalizationTargetNameâ field in it, and if so, is it a different value than the name of the .uplugin file?
Thanks, that all seems correct. I donât suppose you happen to still have the broken PO files in source control, so you can diff them against the working ones?
All we do with the PO files is transform them into LocRes files during cook (so FN can load them), and that should be a fully deterministic process. Iâll see if I can reproduce this myself.
I wasnât able to repro this locally with the steps provided, but I have a few more things to check if you run into this again.
If you open your client logs, you should expect to see a log line like âMounting plugin localization for â<module_id>ââŚâ, where <module_id> can be found in your .uefnproject file.
If you donât see that, then it means the localization data either didnât load or didnât cook. You can find your ValkyrieUploadTemp/<module_id>/ folder and check the .uplugin there; it should have a âLocalizationTargetsâ array, with an entry for your localization target (note: depending on your version of UEFN and project config, it may have been renamed to the <module_id> or it may have kept the friendly name, but either way it should match the target name found in the ValkyrieUploadTemp/<module_id>/Content/Localization/ folder).
Another bug related to translation is happening, all new texts on the map are not being translated, only what has already been translated remains translated
I followed the instructions step by step in case an error occurred again in the translation about seeing the id in the log and in the .uefnproject file and the ids are the same, they are there.
When you say âthese filesâ, do you mean the PO files after the export? If so, that would ultimately be the cause of the missing translations. If you have a log from the editor run where you did the export then that might be useful (you can DM it to me).
The crash seems like one I have a Jira for but also havenât been able to reproduce. I notice that you do have your translation mode set to âAllâ though; that is only really needed when you need to re-translate everything, and you should use âUntranslatedâ by default.
Where can I send a message in your DM? right here on the forum?
When I said âthese filesâ I was referring to the PO files, thatâs correct.
I put the option âUntranslatedâ and it still didnât work.
I had already clicked on âexport localizationâ before recording, notice that all the tracker texts are translated, except this text on the button and the poster next to it written ânew mapâ which are texts that I recently added
And I know that I have to click on âpush changesâ after compiling, I had already compiled it once before
Yeah, if you go to my profile, then click âInteractionsâ, you should see a âMessageâ button near the top-right of the screen.
Okay. If the PO files arenât getting updated correctly by the export then thatâs the root issue youâre seeing, as thatâs how we get the source text to be translated, and is how we compile the translations for use at runtime. Iâm hoping your log will have some clues in it.
I hit this myself internally when testing a different project, and it was an issue caused by URC reverting the file on disk because it thought it was unchanged. Iâve fixed this for 38.00.
The workaround of deleting the files likely works as it tricks URC into thinking the files are an add rather than an edit.
