OS Localization (Windows CE 5.0)
When you localize your OS design, you adapt the Windows CE operating system (OS) for a specific international market, or locale. Once you have localized the OS design, you build a localized run-time image and test the run-time image to verify that it still works properly.
Platform Builder enables you to create a locale-specific run-time image using the following elements:
- Binary resource (.res) files
- Run-time image configuration filess
- Project and hardware-specific files
- Code pages
- UI elements
- National language support (NLS) files
- Currency symbol
- Locale
When you begin to build a localized run-time image, first verify that the localized .res files and run-time image configuration files are in the appropriate directories. In addition, because strings need to be translated from ANSI to Unicode, verify that the default code page for the selected locale is installed on the computer that you use to build the run-time image. After you have verified these files and have localized the -other elements that are necessary for your OS design, you are ready to build a localized run-time image. You can also set environment variables from the command line to toggle localization on or off during the build process.
During the build process, you can choose to use strict localization. Strict localization requires all .res files to be available during the Makeimg.exe phase, and causes an error if the localization process fails to localize a module. Further, if you do not localize a module, the build process fails to generate a run-time image.
If you do not select strict localization, but have selected a locale and language for building a localized run-time image, Platform Builder constructs an image using non-strict localization. Non-strict localization does not require all of the .res files to be available during the Makeimg.exe phase of generating a run-time image. Any missing .res files cause Platform Builder to retain the U.S. resources for the corresponding modules. Platform Builder also generates a corresponding warning for each missing .res file. You can use non-strict localization during the debug process to retest modules without having to have all of the .res files localized.
See Also
Creating an OS Design with the New Platform Wizard | Creating an OS Design | Localizing a Run-time Image Configuration File
Last updated on Thursday, February 02, 2006
Send Feedback on this topic to the authors