3.1.1.2.4 Conversion Rules for String Values Specified by the Client to the Server

When accepting strings as input parameters for methods where the method allows for both Unicode and 8-bit character representations, the server MUST follow these conversion rules:

If the native type of a property is PtypString8 and the client has specified a property value with the type PtypString, the server MUST convert the Unicode representation to an 8-bit character representation in the codepage specified by the CodePage field of the pStat parameter prior to processing the method.

If the native type of a property is PtypString8 and the client has specified a property value with the type PtypString8, the server MUST leave the 8-bit character representation unmodified while processing the method.

If the native type of a property is PtypString and the client has specified a property value with the type PtypString8, the server MUST convert the 8-bit character representation to a Unicode representation prior to processing the method. The 8-bit character representation is considered to be in the codepage specified by the CodePage field of the pStat parameter.

If the native type of a property is PtypString and the client has specified a property value with the type PtypString, the server MUST leave the Unicode representation unmodified while processing the method.

The following table specifies NSPI methods, which are capable of specifying input parameters containing string values in both Unicode and 8-bit character representations, and methods for which these conversion rules are applicable.

 Method

 Description

NspiModProps

String values can be specified in the input parameter pRow.

NspiSeekEntries

String values can be specified in the input parameter pTarget.

NspiGetMatches

String values can be specified in the input parameter Filter.

NspiResolveNames

String values can be specified in the input parameter paStr.

NspiResolveNamesW

String values can be specified in the input parameter paWStr.

Show: