> # Choosing the Transliteration Mode

> SequeLink supports three transliteration modes:

> - Default transliteration mode (see "Default Transliteration Mode")
> - OS transliteration mode, which is used when the operating system (OS) and database code page are single-byte or multi-byte (see "OS Transliteration Mode")
> - Database transliteration mode, which is used to support Unicode databases or when the operating system and database code pages differ (see "Database Transliteration Mode")

> ### Default Transliteration Mode

> Default transliteration mode can be used with all SequeLink Clients and with SequeLink Servers on Linux, UNIX, and Windows. To use Default transliteration mode, set
> ServiceCodePage=Default.

> Use Default transliteration mode only when you created your service with the standard template. Do not use Default transliteration mode with the service template with enhanced code support.

> - For the ODBC and ADO Clients, the administrator defines this mode when the database code page is a 7-bit or 8-bit code page and matches the code page of the client application.
> - For the JDBC and .NET Clients, the administrator defines this mode when the database code page is a 7-bit or 8-bit code page and has a binary-compatible transliteration to UTF-16. In other words, it is possible to convert from the single-byte database code page to UTF-16, by setting either the higher or lower byte to zero.

> ### OS Transliteration Mode

> OS transliteration mode can be used when the operating system (OS) and database code pages use a single-byte or multi-byte character set. OS transliteration mode is useful for European and Asian languages. To use OS transliteration mode, set ServiceCodePage=OS.

> Use OS transliteration mode only when you created your service with the standard template. Do not use this mode with the service template with enhanced code support.

> To configure operating system environment settings:

> - On Linux and UNIX, set locale settings for the service, for example, using the LC_ALL environment variable. Consult your system administrator for the supported values for the LC_ALL environment variable, and to find out which locale settings are supported on your system.
> - On Windows, set regional options on the Control Panel.

> Table 12-2 provides the database transliteration settings to use when configuring a SequeLink service.

> Table 12-2. Defining Database-Specific Settings for OS Transliteration Mode
> Database | Requirements
> --- | ---
> DB2 | No additional configuration required.
> Informix | The code page is set through the service template to a default value: CLIENT_LOCALE.
> Oracle | Setting and determining the operating system code page is operating system-dependent. The operating system code page, the database code page, and the code page configured through the NLS_LANG environment variable must be compatible.
> SQL Server | No additional configuration required.
> Sybase | Set the connection option of the DataSourceSYBConnectOptions service attribute so that it refers to the same (or compatible) code page as the operating system code page. See "DataSourceSybConnectOptions" for details.
> JDBC Socket | No additional configuration required.
> ODBC Socket | Refer to the documentation of the backend ODBC driver for information on passing the operating system code page to the driver as the application code page. On Linux and UNIX, configure the DataDirect Driver Manager with the correct IANAAppCodePage. You can use the ivcheckcp utility to determine the IANAAppCodePage setting. For information about using this utility, refer to the SequeLink Troubleshooting Guide and Reference.

> ### Database Transliteration Mode

> Database transliteration mode is used when connecting to Unicode databases or when the operating system and database code pages differ. To use Database transliteration mode, create a service using the service template with enhanced code page support, which automatically sets the service attributes to the correct settings for database transliteration mode.

> See Table 12-3 for database-specific transliteration settings.

> Table 12-3. Defining Database-Specific Settings for Database Transliteration Mode
> Database | Configuration Requirements
> --- | ---
> DB2 for Linux/UNIX /Windows | No additional configuration required.
> DB2 for z/OS | No additional configuration required.
> Oracle | Configure the NLS_LANG environment variable to be compatible with the database code page.
> SQL Server | No additional configuration required.
> Sybase | No additional configuration required.
> ODBC Socket | Refer to the documentation of the backend ODBC driver for settings that impact or enable the SQL-W function behavior. On Linux/UNIX, configure the DataDirect Driver Manager with the correct IANAAppCodePage. You can use the ivcheckcp utility to determine the IANAAppCodePage setting. For information about using this utility, refer to the SequeLink Troubleshooting Guide and Reference.
> NOTE: Database transliteration mode is not supported with SequeLink Servers for Informix or JDBC Socket, and cannot be used with SequeLink Client for ADO.