Character encodings in Campaign

On most operating systems, Campaign uses the GNU iconv library. Note that Unica does not ship an iconv for AIX installations. For an AIX system, you must obtain the appropriate character sets. For a list, see the National Language Support Guide and Reference:

http://moka.ccr.jussieu.fr/doc_link/en_US/a_doc_lib/aixprggd/nlsgdrf/ iconv.htm#d722e3a267mela

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp? topic=/com.ibm.aix.nls/doc/nlsgdrf/nlsgdrf.htm

This section lists the encodings that are supported by Campaign. The values in these lists are valid values for setting the Campaign internationalization parameters listed in Set Campaign language and locale property values. Note the following:

Each bullet within an encoding group is a space-separated list of different names for the same encoding. Each name in a bullet with multiple names is an alias for the other encodings in the group. You can set the Campaign configuration parameters to any of the values in a group, depending on how your system uses the encodings.

When setting values for the Campaign StringEncoding configuration parameters, the pseudo-encoding WIDEUTF-8 is the recommended value in most cases. However, you can use one of the encodings included in the following lists. Additionally, if the database is DB2 or SQL Server, you should use a code page rather than one of the encodings in this list. For details, see the context help or the Marketing Platform Administrator's Guide.

Campaign uses two character encodings that are treated slightly differently than other encodings: “ASCII” and “UTF-8.” Both are case-sensitive. These encodings are accepted on all platforms including AIX. They have slightly different behaviors in Campaign for column widths during table mapping, and for transcoding operations.