Partager via

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

  • Article

Send Feedback

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 Platform.

  2. Complete the New Platform Wizard to create a basic OS design using the appropriate design template, such as an Enterprise Web Pad.

  3. In the Catalog, expand the International node, locate the Unicode Processor for Complex Scripts Catalog item, and drag it to the Workspace window.

  4. 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.

  5. From the Platform menu, choose Settings. The Platform Settings dialog appears.

  6. In the Platform Settings dialog box, on the Locales tab, 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.

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

  8. Clear Localize the build , and then choose OK.

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

  10. 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.

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

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

  13. 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

  14. In Platform Builder, from the Build OS menu, choose Sysgen to build your run-time image. Make sure that the Copy Files to Release Directory After Build and Make Run-Time Image After Build options are selected.

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

See Also

Complex Scripts Support in Windows CE | Uniscribe OS Design Development

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.