Overall translations for a language in Mobile WMS consist of:
- Device Language = The language of the Android App ("static" messages i.e., translations for buttons, menus, page headers at the Mobile Device). This is a resource file deployed to each Mobile Device and will require special tools to edit and deploy.
- Mobile Language = These are translations used by the Document Handler codeunits in Mobile WMS ("dynamic" messages), also called Mobile Messages. These messages can be displayed and edited from the web client.
- Error messages from standard BC posting routines = Error messages thrown from the standard BC posting routines are always displayed in the language of the web service tier, regardless of the Device Language and Mobile Language is setup for the mobile user.
Generally, if a specific translation cannot be found the US English (ENU) translations will always be displayed.
Out-of-the-box you can select from ~16 different Device Languages and 3 different Mobile Messages Languages (DAN, DEU and ENU). You can combine these as you wish.
Note, in the screenshot below, only three Mobile Language Codes (DAN, DEU and ENU) has associated Messages – meaning i.e., mobile users associated with language code "ESP" will display device language translations from the associated device language "ES" for "static" messages on the mobile device - but will fall back to ENU for everything else (all messages generated from the Document Classes).
Using the "Create Messages" and (edit) "Messages" actions from the "Mobile Languages" page above you can edit/create messages for any Mobile Language to improve the user experience for countries not fully supported in the standard Mobile WMS.
The Device Language and Mobile Language are further explained in the next sections.