In
Silk Performer, expand the
Profiles node in the
Project tree.
Right-click the profile that you want to configure and choose
Edit Profile.
Tip: Alternatively, you can choose
Settings
> Active Profile from the menu bar.
The
Profile - [<profile name>] dialog box opens, and the
Replay category is displayed in the shortcut list on the left.
In the shortcut list on the left, click the CORBA/IIOP icon.
Click the WChar / WString tab.
Use the Code set area to specify the settings for the wide-character code set.
In general, a code set determines the encoding rules for characters and wide characters. Code sets can be byte-oriented or
non-byte-oriented (for example, ASCII is a byte-oriented code set for single byte characters). Multibyte characters defined by non-byte-oriented code sets have
a byte-orientation (big-endian, little-endian); byte-oriented code sets do not.
Check the Unicode
check box to use the Unicode code set.
Unicode is a non-byte-oriented code set for two-byte characters. The byte orientation of Unicode characters is determined
by the IIOP message byte order.
From the WChar size list box, select the size of a CORBA wide character (wchar).
Click the Byte-oriented option button to have a byte-oriented code set used for CORBA wchars and wstrings.
Alternatively, click the Non-byte-oriented option button to use a non-byte-oriented code set for CORBA wchars and wstrings. If you select this option, use the Script byte order list box to select the byte orientation of non-byte-oriented CORBA wchar/wstring representation in the BDL script. The byte
orientation can be little-endian (least significant bit first) or big-endian (most significant bit first).
Note: Use the IIOP 1.2 area to specify settings for IIOP 1.2. The wchar and wstring encoding in IIOP 1.2 differs from the encoding in previous IIOP
versions. However, not all ORBs use the correct encoding for IIOP 1.2.
Check the CORBA compliant check box if the ORB uses CORBA compliant wchar/wstring encoding in IIOP 1.2.
In the WChar area, check the No length encoding check box to use pre IIOP 1.2 encoding.
CORBA compliant IIOP 1.2 encoded wchars use a length indication for the size of the wchar.
In the WString area, check the Null-terminated check box if the ORB uses null-terminated wstrings.
CORBA compliant IIOP 1.2 encoded wstrings are not null-terminated.
Click the Chars option button if the ORB uses the number of chars as wstring length.
CORBA compliant IIOP 1.2 encoded wstrings specify the string length in bytes (chars).
Alternatively, click the WChars option button if the ORB uses the number of wchars as wstring length.