Sometimes it is easier to generalize a problem and solve the general case.
If I were to internationalize a multi-screen app, I would use TinyDB instances (NameSpaces) as my cross-language encoders and decoders.
I would code the app for what I like (English), and load the Media folder with language files, 2-column CSV tables of English, foreign phrases from my Labels, Notifiers, ListView elements, etc.
Sample files:
German.csv:
"No","Nein"
"Stop","Halt"
(... I have forgotten all my German)
Spanish.csv:
"Yes","Si"
"mister","senor"
(I learned my Spanish from Mel Blanc)
When the user chooses German from the language list, read the German.csv file from Media, and when it arrives load a TinyDB instance (TinyDBTranslate, Namespace=Translate) with English tag / German value pairs .
Have all the screens use the TinyDBTranslate lookup to decide what to show based on what the component had in its .Text attribute left over from the Designer, or what was in your text blocks that you wanted to display.
If you need to reverse translate, like from a Notifier response, use a reversed (values/tags) TinyDB loaded from the same language file.
This avoids having to keep blocks for every phrase and every language, if you use the Any Label and Every Label blocks.