Character vs. Byte

In the manuals of SBCS PM API, the expression number of characters in the string is often used. When you handle mixed strings, you should read the above expression as number of bytes in the string since the terms characters and bytes are not equal any more. For example, you should specify the number of bytes in the Count parameter of GpiCharString.

Several PM calls use a vector, as a parameter, of which each element corresponds to each character of a string. In DBCS PM, each element of the vectors corresponds to each byte. For example:

• alAdx (increment values) of GpiCharStringPos , GpiCharStringPosAt.

  For a DBCS character, the element that corresponds to the first bytes of the DBCS character can contain increment value for that character, but the element that corresponds to the second byte is ignored.

• alXincrement (increment values) of GpiQueryCharStringPos, GpiQueryCharSTringPosAt.

  The same as the above.

• aptlPositions (increment values) of GpiQueryCharStringPos, GpiQueryCharSTringPosAt.

  For a DBCS character, the element that corresponds to the first bytes of the DBCS character is the position of that character; but the element that corresponds to the second byte is unknown.