Consider I18N as integral part of initial development, with solid functions to support the translation efforts.
Users can switch to another language any time without delay during runtime, thus enabling multilingual companies to ease collaboration between employees or support persons.
Adjust to language requirements including semantic positions of variables into the targeted text e.g. for messages.
While creating models, element ids and -names are automatically collected into property files, delivering a default translation in the language you used for your element descriptors.
With the smart online translator framework based on the TapiJI project, you fix improper translations and find unresolved translations.
Generate initial translations using the Google Translator API, easily connect via the IDE preferences dialog.