Description
| Excerpt |
|---|
todo |
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.
he language of the Mobile App is controlled via "Device Language Codes".
How to change language
- "Mobile Languages" can be assigned to each mobile user.
- "Device Language Codes" are assigned to "Mobile Languages".
| Anchor | ||||
|---|---|---|---|---|
|
Device code | Country | Device code | Country |
DA | Danish | LT | Lithuanian |
DE | German | NL | Dutch |
EN | English | NO | Norwegian |
ES | Spanish | PL | Polish |
ET | Estonian | PT | Portuguese |
FI | Finnish | RO | Romanian |
FR | French | RU | Russian |
IT | Italian | SE | Swedish |
*) Additional languages for the Android App exist and can be deployed upon request - but are not deployed with a standard installation of the Android App at the time of writing, including Czech (CS), German Haas customized (DE_HAAS), Flemish (NL-BE), Chinese (Hong Kong ZH-HK) and Japanese (JA).
| Anchor | ||||
|---|---|---|---|---|
|
Device code | Country | Device code | Country |
CZ | Czech | HK | Chinese (Hong Kong) |
DE | German | IT | Italian |
DE_HAAS | German, Haas customized | JP | Japanese |
DK | Danish | NL | Dutch |
EE | Estonian | NO | Norwegian |
EN | English | PL | Polish |
ES | Spanish | PT | Portuguese |
FIN | Finnish | RO | Romanian |
FLEMISH | Flemish | RU | Russian |
FR | French | SV | Swedish |
| Anchor | ||||
|---|---|---|---|---|
|
When the Device Language associated to a Mobile User is changed, the mobile device Login Screen will display in this language starting at the second login. The reason being no user is logged in when still at the login screen, hence it is no way of knowing the associated device language for the user until first login is executed. It is possible to lock the login screen of a mobile device to always display in a specific language by changing the start.cfg
Please ask the Service Desk for assistance.
| Anchor | ||||
|---|---|---|---|---|
|
Overview
| Page Tree | ||||
|---|---|---|---|---|
|