Multi Language Support
Creating multi language applications is easy with WEM. The tools and functionality are all there. How you
use those in your project is something to think about before you start.
Multi language support in WEM is available through a global dictionary. Here you define symbols that are used as placeholders for the content, in the various languages you want to support. We always use the primary language as the symbol. In your WEM models, wherever you want to show text, you use the symbol instead of the actual text. For example, if your application supports English and Dutch and you need the word “Turtle”, you would create a dictionary entry for the symbol $turtle with the words for English “Turtle” and Dutch “Schildpad” in the appropriate columns. You would now use $turtle in your user interactions, buttons and so on. Depending on the language chosen for the interface, the right content would be retrieved from the dictionary.
The available languages are set per project and the language strategy can be set per portal. That means, you could publish separate portals for each language from the same project. Possibly even with a complete different look and feel by changing the master template (CSS), but that’s for another blog. For each portal you set the language strategy and default language, the language strategy can be either “Fixed”, “Browser default” or “User selectable”.
Selecting a language doesn’t just change the dictionary that is used. The date and time format, currency and if applicable sort order are also adjusted to that language’s standards. The selected language is also available as a function in your own projects, so you can use this value to make functionality optional or automatically modify your ontology knowledge matrix.
These complete language strategies allow you to create international applications across HTML5 devices rapidly. Maybe we should consider changing our tagline to “Custom software for a global market, without programming.”