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 function is an application-defined callback function. It is called as a result of a call to the EnumUILanguagesfunction, and receives a pointer to a string buffer containing a UI language identifier.

Syntax 

BOOL CALLBACK EnumUILanguagesProc(
  LPTSTR 
lpUILanguageString
);

Parameters

lpUILanguageString

Pointer to a string buffer containing a null–terminated string that specifies the UI language identifier ( LANGID). For example, the system–defined language identifier for English (United States) is 0x0409. For more information about language identifiers, see Language Identifiers and Locales.

Note:
The lpUILanguageStringparameter should be an LPWSTR for the Unicode (W) version of EnumUILanguagesProc.

Return Value

TRUE continues enumeration. FALSE stops enumeration.

Remarks

EnumUILanguagesProcis a placeholder for an application–defined function name. An EnumUILanguagesProcfunction can carry out any desired task. An application registers an EnumUILanguagesProcfunction by passing its address to the EnumUILanguagesfunction. A value of type UILANGUAGE_ENUMPROC is a pointer to an EnumUILanguagesProcfunction.

Note:
This function poses a security risk. The parameter lpUILanguageStringis only used as input but not declared as a const string. The user may fill anything into it and can cause a buffer overflow.

Requirements

Header windows.h
Library Coreloc.lib
Windows Embedded CE Windows CE .NET 4.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

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.