To support multiple languages concurrently, you can choose UTF-8 as your codepage (for details on how, see the procedure http://www.attunity.com/forums/data-...4.html#post954). Data is then saved as Unicode in UTF-8 encoding.

Note: This option is not supported on EBCDIC platforms.
It is also important to remember that if you choose UTF-8 as your codepage for concurrent multiple language support, all string-type data in your database will be stored in UTF-8 encoding.

There may be cases in which some of your existing data is encoded differently, for example with 7-bit encoding. AIS allows you to specify which fields are encoded differently by using the NLS_STRING data type. Data fields of this type are converted from the alternate encoding to the main encoding that you set in the procedure http://www.attunity.com/forums/data-...4.html#post954 for your environment, when read from the database, and converted back to the alternate encoding when writing to the database.

To define the nlsString codepage
1. In Studio, navigate to the Design perspective.
2. In the Configuration view, right-click the machine with the binding configuration you want to set.
3. Under the Bindings node, select the relevant binding configuration.
Note: NAV is the default binding.
4. Right-click the binding configuration and choose Edit Binding.
The environment properties are listed in the Properties tab. nlsString is set under the misc group.
5. In the Value field for the nlsString property, specify the codepage to be used for non-UTF-8 encoding.