When trying to re build auto localization it shows me this error. I dont have a way to know what is going wrong
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Other
Steps to Reproduce
Build auto localization once
Build auto localization again
Expected Result
Failed to create auto localization
Observed Result
LogValkyrieAutoLocalization: Error: [Failure] Auto Localization - Failed to create an auto localization job for module ‘85ac65d2-4ef3-e430-16c3-6688344dbe23’: source string cannot be empty (input.sourceStrings[65].source)
If you check the PO file for your native language (found at Content/Localization/<project_name>/<native_language>/<project_name>.po) and search for “”, then that should hopefully identify the empty string and let you remove/edit it from its source location.
I would be curious to know what you find, as we don’t usually gather empty strings for localization. I suspect Verse may be missing some of the guards we have for text gathered from assets.
Regardless, I’ll also guard the auto localization job input against empty strings (likely in 39.10), but that won’t help you today.
Failed to create an auto localization job for module '55bb032d-4f01-350e-2e20-ac9e49b43ac4': source string cannot be empty (input.sourceStrings[203].source)
Do you want to continue without localization data?
Checked the Localization files in:
%LOCALAPPDATA%\UnrealEditorFortnite\Intermediate\ValkyrieLocalizationTemp\
Went to my Project Folder: Rewindead
Removed the Rewindead.ugcloc
Open with VSCode Rewindead\en\Rewindead.po
I had ““ on line 3 & 4 - tried changing it, commenting it out, and deleting it, all with the same issue.
Okay, the first empty string is part of the PO file header so you can ignore that one. It sounds like you don’t have any empty strings gathered at least, so I’m not sure where that’s coming from.
How much text do you have in each of your projects? After running the first auto localization job are you also importing the result before running the second?
We’ve identified the cause as whitespace only strings (so the error was slightly misleading). A fix for the immediate error should be deployed tomorrow, but you may notice that auto localization still thinks the whitespace only strings are unlocalized.
I’ll also fix some inconsistencies in how we gather the text itself, as we don’t usually gather whitespace only strings in UE, but the Verse part of the gather is currently allowing it. That part of the fix will go out in 39.10.