OS Localization (Windows Embedded CE 6.0)
1/6/2010
When you localize your OS design, you adapt the Windows Embedded 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 by using the following tools:
- binary resource (.res) files
- run–time configuration files
- project–specific files
- hardware–specific files
- code pages
- localized UI elements
- national language support (NLS)
- Unicode
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. Then, 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 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. This can be useful because the build process guarantees that your OS design is fully localized.
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.
In This Section
- Binary Resource Files
Provides a description of the file that holds all of the strings, graphics, and other localizable objects used by Windows Embedded CE.
- Run-time Image Configuration File Localization
Provides a description of the ANSI file that contains operating specifications for the hardware and software on your target device.
- Project and Hardware-specific File Localization
Describes the options to localize project–specific or hardware–specific files during the Makeimg.exe phase.
- Displaying Localized Font Files Correctly in a Run-time Image
Provides a list of steps to add fonts to a locale's image.
- Configuring the NLS Table
Describes the tables that contain the locale identifiers (LCIDs) available to your OS design.
- Enabling an Additional Code Page on an OS Design
Provides instructions on including extra code pages in the OS design.
- Week Number Implementation
Provides instructions to modify the registry settings that define which system is used to determine the first week of the year.
- UI Element Localization
Provides a list of the UI elements that are tested for displaying correctly at different screen resolutions regardless of the locale.
- Currency Symbol Localization
Provides instructions to add new currency symbols to the system.
- Locales for Localized Run-Time Images
Lists the locales for which localized resource files are available.
Related Sections
- International OS Design Development
Provides a discussion of the options and programming elements available for adding international components to Windows Embedded CE.