Create a wince6.0 system that supports complex scripts

To create a system that supports complex scripts (complex scripts), we need to complete the following steps to ensure that the system contains all the specific region settings that need to be supported (locale-specific ).

 

1. Select the Unicode processor for complex scripts component under International

Figure 1

This component corresponds to the system environment variable sysgen_uniscribe.

 

2. Add a specific locale

Add the support for specific locale to the system from the Pb directory. For example, if we want to include Arabic in the system, find the Arabic file in international \ locale specific support in Pb, select the appropriate font and keyboard, as shown in figure 1.

 

3. Select the specific locale in property pages under the project

Figure 2

In the List Directory, select the appropriate locale for our system. The selected locale contains the required NLS (National Language Support, international language support) the default OEM code page corresponding to the corresponding ANSI (American National Standards Institute) and locale (character set and character encoding scheme, codePage is the ing table between the character encoding and Unicode in different countries)

 

In Figure 2, select default locale and clear

 

 

4. create common. Str required by locale

 

Open the \ wince600 \ public \ common \ oak \ files \ intltrns folder, create a folder, and name it with lcid (locale identifier). This lcid will be used as the system's default lcid. For example, if you want to create a system with the default lcid of Arabic (Saudi Arabia, Saudi Arabia), name this folder as 0401.

 

Copy the common. STR to the 0409 folder from intltrns \ 0401 (English) and open this file to modify the following definition:

# Define loc_lcid ~ "<Default lcid>"

# Define loc_acp ~ "<Default code page>"

# Define loc_hkl_default ~ "<Default HKL value>"

For Saudi Arabia, the values defined above are as follows:

# Define loc_lcid ~ "401"

# Define loc_acp ~ "4e8" // 1256, Ara

# Defineloc_hkl_default "00000401"

Figure 3

Note that both lcid and the default code page must be in hexadecimal format. The following table lists the HKL of the complex script locale.

Figure 4

 

5. SelectSCompile and run ysgen

After sysgen is compiled and updated, the wince interface is as follows:

 

Figure 5

The display of my device is also from right to left, for example:

Figure 6

But why is it displayed in English? PB files like Arabic do not directly provide res files. Of course, these res files can be created by yourself (just create a dialog box, add a button, edit a box, and so on), provided that you understand the relevant language. If you select the Arabic language in Pb-> setting-> Local, your compiled NK will always be in English. Because when makeimage is used, if the res file of the relevant language is not found, the default 0x0409 is used.

 

 

In wince6.0, WordPad, inbox, Windows Messenger, and file viewers do not support complex scripts.

Figure 7