Thank you Norman, for this extra insight.
I was just lately setting up some language Constants for the first time, but I was also setting the “Localized” setting to “On” for each entry (assuming I had to).
Because “Localized” was “On”, the “Build Settings > Shared > Language” choice didn’t seem to make a difference when I ran my app with my English language OS. But I did see that if I reboot into another language, e.g., French, then my app would display in French.
So I guess for the purpose of tweaking my Desktop app layout, to ensure I have enough room for some long worded translated phrases, e.g., German, Italian, etc., I should have my Constants “Localized” setting to “Off”, so I can more easily switch between translated text during development - so I don’t have to reboot my machine into another language for testing?
And then, when I’m ready for the “Final” build, either:
A.) - Turn all the “Localized” settings back to “On”, for a single distributed app?
B.) - Leave the “Localized” settings “Off” and do separate builds for each supported language?
Or am I over thinking this, or not understanding something?
Any advice would be appreciated.
Note: The one benefit I did see to the “Build Settings > Shared > Language” choice, was if I use the #App.MultiLanguagePhrase
syntax for Constants in the IDE Text/Caption inputs for Label & Button controls, the text would display in the chosen language in the IDE design views. But that syntax didn’t seem to work for all controls.