In wince5, Pb comes with res files in 12 languages. These files are system dialogs, menus, and other resources in the corresponding language. These 12 languages are:
0x0404 Chinese Taiwan
0x0407 German Germany
0x0409 English us
0x040c Franch France
0x0410 Italian Italy
0x0411 Japan
0x0412 Korean Korea
0x0413 Dutch newtherlands
0x0416 Portuguese Brail
0x041d Swedish Sweden
0x0804 Chinese PRC
0x0c0a Spanish Span
That is to say, after compiling in one of the above 12 languages in Pb-> setting-> local, the system is the system of the corresponding language, but if you want to support the input method and font, you still need to add relevant input methods and font components. However, 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 addition, WinCE also provides the following support for locale-specific. In help, locale-specific includes fonts, keyboards and keyboard drivers, and Input Method Editors (IMES ), and input methods (IMS ).
Arabic
Chinese (simplified)
Chinese (traditional)
English (U. S .)
English (worldwide)
French
German
Hebrew
Indic
Japan
Korean
Thai
That is to say, the input method or font library wince in the above language are provided in the form of components, which can be found in Pb catalog. The following section describes the complex script (copy from Pb help) a complex script has at least one of the following attributes:
- Allows bidirectional Rendering
- Has contextual Shaping
- Has combining characters
- Has specialized Word-breaking and justification rules
- Filters out illegal character combinations
Bidirectional rendering refers to the script's ability to handle text that reads both left-to-right and right-to-left. For example, in the bidirectional rendering of Arabic, the default reading
Direction for text is right-to-left, but for some numbers, it is left-to-right. processing a complex script must account for the difference between the logical (keystroke) Order and the visual order of the glyphs. in addition, processing must properly deal with caret movement and hit testing. the mapping between screen position and a character index for, say, text selection or caret display requires knowledge
Of the layout algorithms. Contextual shaping occurs when a script's characters change shape depending on the characters that surround them. This occurs in English cursive writing when a lowercase "L" changes shape depending
On the character that precedes it such as an "A" (connects low to the "L") or an "O" (connects high ). arabic is a script that exhibits contextual shaping. combining characters (ligatures) are characters that join into one character when placed together. one example is the "AE" Combination in English; it is sometimes represented by a single character.
Arabic is a script that has combining characters. specialized word break and justification refers to scripts that have complex rules for dividing words between lines or justifying text on a line. thai is such a script. filtering out invalid character combinations occurs when a language does not allow certain character combinations. thai is such a script.
Windows CE provides the support for complex scripts and allows run-time images to be created for the following locales:
- Arabic
- Gujarati
- Hebrew
- Hindi
- Kannada
- Marathi
- Punjabi
- Tamil
- Telugu
- Thai
The Windows CE support for complex scripts schemdes:
- Uniscribe scripting engine.
- Processing ing.
- Complex scripts in Graphics Device Interface (GDI), common controls, and graphics, drawing wing, and events subsystem (GWES ).
- Complex scripts Content Rendering and intrinsic control support in Internet Explorer 6 for Windows CE.
Note Windows CE does not support complex script input through the command line (cmd.exe ).
Windows CE also does not support printing for complex scripts.
Applications that are not enabled for complex scripts
- The following Windows CE applications are not enabled for complex scripts:
- Microsoft Pocket Internet Explorer
- Instant Messenger
- Word pad
- Inbox
- File viewers
When creating a complex scripts-enabled run-time image, you need to complete a set of steps to make sure your run-time image between des all the required locale-specific support. to create a complex scripts-enabled run-time image
- In platform builder, from the File menu, choose new platform.
- Complete the new platform Wizard to create a basic OS design using the appropriate design template, such as an enterprise web pad.
- In the catalog, expand the international node, locate the Unicode processor for complex scripts catalog
Item, and drag it to the workspace window.
- 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
Underinternational \ locale specific support and select the appropriate font and keyboard catalog items.
- From the platform menu, choose settings. The Platform
Settings dialog appears.
- In the Platform Settings dialog box, on the locales tab, select the appropriate locale
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.
- From the default language drop-down list, select the default language for your run-time image.
- Clear localize the build, and then choose OK.
- In Windows Explorer, navigate to the % _ winceroot % \ public \ common \ oak \ files \ intltrns directory.
- 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
Lcid that defaults to Arabic (Saudi Arabia), name the new folder "0401." For a list of locale identifiers, see language
Identifiers and locales.
- In the % _ winceroot % \ public \ common \ oak \ files \ intltrns directory, navigate to the 0409 folder, and copy the common. Str file.
- Open the folder for your default lcid that you created in step 10, and paste common. Str into this folder.
- 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.
This article is from the "bluefish" blog, please be sure to keep this source http://bluefish.blog.51cto.com/214870/73451
