Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This message is sent to an application when the IME gets a character of the conversion result. Unlike the WM_CHARmessage, this message can include double-byte as well as single-byte character values.

Syntax 

chCharCode1 = (WORD)
wParam;
lKeyData = 
lParam
;

Parameters

chCharCode1

For double-byte character sets:Specifies a single- or double-byte character value. For a double-byte character, chCharCode1contains the lead byte.

For Unicode:Specifies a Unicode character value.

chCharCode2

For double-byte character sets:Specifies a single- or double-byte character value.

lKeyData

Specifies the repeat count, scan code, context code, and conversion-state flag.

The following table shows the values that this parameter can take.

Value Description

0–15

Repeat count: Because the first byte and second byte is continuous, this is always 1.

16–23

Scan Code: Scan code for a complete FE character.

24–28

Not used.

29

Context code.

31

Conversion state.

Return Value

None.

Remarks

If the WM_IME_CHARmessage includes a double-byte character and the application passes this message to the DefWindowProcfunction, the IME converts this message into two WM_CHARmessages, each containing one byte of the double-byte character.

Requirements

Header imm.h
Windows Embedded CE Windows CE .NET 4.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

Other Resources

DefWindowProc
WM_CHAR

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.