Creating a Complex Scripts-enabled Run-Time Image (Windows Embedded CE 6.0)

1/6/2010

When creating a Complex Scripts–enabled run–time image, you need to complete a set of steps to make sure your run–time image includes all the required locale–specific support.

To create a Complex Scripts-enabled run-time image

1. In Platform Builder, from the File menu, choose New, and then choose Project.

2. In the Name box, type a Name for your OS design, and choose OK.

3. Complete the Windows Embedded CE OS Design Wizard to create a basic OS design using the appropriate design template, such as an Enterprise Web Pad.

4. In the Catalog, expand the International node, locate the Unicode Processor for Complex Scripts Catalog item for the language you want to support (SYSGEN_UNISCRIBE), and select the corresponding check box.

5. From the Catalog, add the locale–specific support to your run–time image. For example, if you want to include support for Arabic in your run–time image, navigate to the Arabic folder under International\Locale Specific Support and select the appropriate font and keyboard Catalog items.

6. From the Project menu, choose <SolutionName> Properties. The <SolutionName> Property Pages dialog box appears.

7. In the <SolutionName> Property Pages dialog box, expand Configuration Properties, and choose Locale.

8. In the Locales list, select the appropriate locale for your run-time image. Selecting the target locale will include the required NLS data and the associated ANSI and default OEM code pages for that locale.

   Note

   You can clear any of the locales that are selected by default.

9. From the Default locale drop–down list, select the default language for your run-time image.

10. Clear the Localize the build box, and then choose OK.

11. In Windows Explorer, navigate to the %_WINCEROOT%\PUBLIC\COMMON\OAK\FILES\INTLTRNS directory.

12. Create a new folder and name it with the locale identifier (LCID) that will be the default LCID for your run–time image. For example, if you want to create a run–time image with an LCID that defaults to Arabic (Saudi Arabia), name the new folder "0401". For a list of locale identifiers, see Language Identifiers and Locales.

13. In the %_WINCEROOT%\PUBLIC\COMMON\OAK\FILES\INTLTRNS directory, navigate to the 0409 folder, and copy the Common.str file.

14. Open the folder for your default LCID that you created in Step 10, and paste Common.str into this folder.

15. Open the Common.str file you just pasted and change the following values to the default LCID of your run–time image:

    #define LOC_LCID    ~"<default LCID>"
    #define LOC_ACP    ~"<default code page>"
    #define LOC_HKL_DEFAULT    ~"<default HKL value>"
    

    Save Common.str.

    Note

    The values for the LCID and default code page have to be hexadecimal.

    The following table lists the Handle to the Keyboard Layout (HKL) values for the Complex Scripts locales.

    Locale	HKL value
    Arabic	00000401
    Hebrew	0000040D
    Thai	0000041E
    Hindi	00010439
    Tamil	00000449
    Kanada	0000044B
    Gujarati	00000447
    Telugu	0000044A
    Punjabi	00000446
    Marathi	0000044E

16. In Platform Builder, from the Build menu, choose Global Build Settings, and make sure that the Copy Files to Release Directory After Build and Make Run-Time Image After Build options are selected.

17. Choose Sysgen to build your run-time image.

    Note

    The following applications are not enabled for Complex Scripts: WordPad, Inbox, Windows Messenger, File Viewers.

See Also

Concepts

Complex Scripts Support in Windows Embedded CE
Uniscribe OS Design Development