I use the following solution:

I exported the texts in all languages ​​(with UID) from Passolo and saved them in a variable table in ST4.

When writing the texts, I insert the variable and the translations are automatically and correctly available.

That sounds simple enough for me to accomplish. Any bascklashes?

no, it works

What export format do you use? And do you create one export file per language?

I exported csv format per language and then inserted all languages ​​into a spreadsheet (1 column per language).
Requirement: all texts are available in all languages.

Finally, this Excel list can be saved in ST4 in the variable node, as shown in the picture above.

Thank you so much. This is a very promising starting point. My first experiments reveal some issues, such as identical string IDs, or UI strings using variables. But nothing that would discourage me at the given point. Thanx again. I might be in touch again, though...

Thank you so much. This is a very promising starting point. My first experiments reveal some issues, such as identical string IDs, or UI strings using variables. But nothing that would discourage me at the given point. Thanx again. I might be in touch again, though...

Depending on the resource file formats (WPF vs. DLL/RC) IDs might be not unique. Additional information like resource/dialog IDs must be exported as well.

Messages with placeholders are another challenge. Passolo doesn't know what will be inserted during runtime and need to post-process the export or customize the export in a way that Passolo inserts some useful data into the placeholders.