Handling International Character Sets with EOF
Synopsis
Describes how to configure Enterprise Objects Frameworks (EOF) to handle international character sets with Oracle, Sybase, and Informix databases.
Discussion
When using databases such as Oracle, Sybase, or Informix, you can configure EOF to handle the character set used in the database. If you don't configure it, your application may read and write incorrect characters from the database, and display them incorrectly. For example, an unconfigured application will display "il _tait une fois..." instead of "il était une fois". Only strings with extended characters (ASCII code greater than 127) are affected.
You can configure the character set to be used with EOF by adding information to the connection dictionnary of your EOModel file under two keys.
The first key is databaseEncoding . This key tells the Foundation Classes which encoding to use when it builds strings from char * strings. The possible values for this key can be found in the NSString class documentation in the paragraph about string encoding.
The name of second key depends on the database. It tells the database client library what character set to use for sending or retrieving strings. For Oracle, the key name is NLS_LANG and for Sybase it is LC_ALL . For Informix you must specify two keys: DB_LOCALE and CLIENT_LOCALE .
You can add these keys by using the model inspector inside EOModeler.
The following are some examples of connection dictionaries
Figure 3. Informix
databaseEncoding = "ISO Latin-1"; DB_LOCALE = "en_us.8859-1"; CLIENT_LOCALE = "en_us.8859-1";
Refer to your database documentation to determine the character sets available in your configuration and the names of the environment variables.
When to Configure
Your application will sometimes handle character sets correctly even if you haven't set the connection dictionary values, because EOF uses the environment variables defined in the system when no entries are found in the connection dictionary. However, it is best to set the values in the connection dictionary to avoid potential problems. For example, moving your application to another computer with different environment variables may cause it to fail.
You should also configure the connection dictionary if your application uses a database shared with non-EOF applications. This guarantees that your data will also be read and written correctly by those applications.
When the Connection Dictionary Values are Used
The entries you specified in your EOModel file are used the first time EOF connects to the database.
Databases with Mixed Encodings
Sometimes a database contains mixed encodings. This generally happens when different applications running on different platforms insert or modify values in a database.
One solution to this problem is to use a custom value class to try to figure out and decode the characters at fetch time. You can supply a class with a factory method that takes bytes and a length as arguments. This custom class can try to figure out the correct character set, and then create and return the correct string. The class-and-methods specification is done inside EOModeler by selecting the internal data type as Custom in the Attribute inspector, and filling all appropriate fields.
Note: The custom value class must be written in Objective-C.
Questions
· How can I display strings from my database containing international characters?
· Why are accentuated character strings incorrectly displayed in my interface?
· Why can't other applications read data created from an EOF application?
· Which property entries are available for handling character inside EOF?
· How can EOF work with a database containing mixed encodings?