MUI Implementation (Windows CE 5.0)
The MUI includes resources for each supported UI language, separated from their binaries, and provided in separate language directories. To achieve the goal of user-switchable language in a specific target device, the target device must have the locale data, code pages, and fonts for all the UI languages to be supported. These are configured when the OS design is created or can be added later.
In addition, you must set any needed operating system UI resources in ROM, such as the localized resources for the default language. Additional languages can be included in the run-time image, or potentially installed later.
Typically, you select the set of languages that a target device is capable of supporting by including particular code pages and locales when you build the run-time image. A target device that includes the code-page 1252 would, for example, usually include all of the western European locales that use that code-page. Because the bulky portion of locale support is the code-page, the incremental cost of including all locales that share a code page is small. This target device might ship with the UI resources for say, English and French. If a user later wanted to upgrade the target device to support German as well, they would only need to install the UI resource DLLs for German for the run-time image and for all of their applications.
When you build an MUI-enabled run-time image, you also need to specify the default language of the run-time image. For an example of how to specify the default language for a run-time image, see Creating a Multilingual OS Design.
For information about how to build a multilingual run-time image, see How to Create a Multilingual Run-time Image Using MUI.
See Also
Multilingual User Interface (MUI) OS Design Development | MUI Locale Considerations | Working with Fonts in the MUI
Send Feedback on this topic to the authors