Thanks for replying, but: My statement is that a concat of mutiple separately translated strings is unusable for more complex translations. Instead, the translation system must be able to provide msgstr/msgid in the po files that contain placeholder or similar, because only this way a separate translator person has any chance to give a meaningful translation. Example: “Should the file {0} be deleted?” – the word ordering in the sentence might be changed completely for other languages. Hence, any professional language translation system in software usually supports those placeholders as part of the translatable strings.
Having said that, in https://openui5.hana.ondemand.com/1.52.29/#/topic/df86bfbeab0645e5b764ffa488ed57dc it seems the {0}, {1}, … syntax is already supported in OpenUI5, where the translatable string “Hello {0}” is transformed into “Hello World” in the client script code?