# Localization

## Localized MOF files

All the MOF files used by the NCS2 WMI Provider are localized according to the Microsoft® Windows® Management Instrumentation (WMI) globalization model. To accomplish this, each class definition is separated into the following:

- a language-neutral version that contains only the basic class definition in the .mof file.
- a language-specific version that contains localized information, such as property descriptions that are specific to a locale in the corresponding .mfl file.

## Class Storage

The language-specific class definitions are stored in a child sub-namespace beneath the namespace that contains a language-neutral basic class definition. For example, for the NCS2 WMI Provider, a child namespace ms_409 will exist beneath the root/intelncs2 namespace for the English locale. Similarly, there exists a child sub-namespace for each supported language beneath the root/intelncs2 namespace.

## Runtime support

To retrieve localized data, a WMI application can specify the locale using strLocale parameter in SWbemLocator.ConnectServer and IWbemLocator::ConnectServer calls. If the locale is not specified, the default locale for that system will be used. (e.g. MS_409 for US English). This locale is used to select the correct namespace when adding in the English strings.

In addition, IWbemServices::GetObject, SWbemServices.GetObject, IWbemServices:: ExecQuery, and SWbemServices.ExecQuery must specify the WBEM_FLAG_USE_AMENDED_QUALIFIERS flag to request localized data stored in the localized namespace, along with the basic definition. This is required in all functions that produce displayable values using value maps or display descriptions or other amended qualifiers from the MOF files.

Home

Copyright© 2004 Intel Corporation. Legal Information