A small update: setting PO file importing aside, I had some success with working with LocRes files. In-engine preview seems to work well. However I’d still like to utilize importing PO files to better integrate with the Localization Dashboard (word count, compiling, etc. to better fit in with Unreal’s standard localization workflow).
Also, the “strange behavior” regarding preview strings popping on and off seems to have been a mistake from my part - I had mixed in code that deals with LocRes and that seems to have affected it. I’ve now separated processing LocRes files from dealing with PO files - and the LocRes function seems to work as expected.
Some things I forgot to mention in the original post:
- I am not using revision control.
- I am testing with 1 target (Game) and 1 culture (French “fr” for now), just to keep things simple for now.
- Source strings are not being modified.
I noticed that there may be an additional step in the standard workflow using the Localization Dashboard, where after importing a PO file, there is an optional step to “Choose Translation”. I am also suspecting that there may be information passed onto the parent window, or some delegate that I have to handle. I am quite lost in this regard - any help would be appreciated!