Neoview Character Sets Administrator's Guide (R2.4, R2.5)

character is mapped to a plane within the Unicode encoding and equivalent characters are
mapped to the same Unicode code point. Java-based Neoview client applications such as Neoview
DB Admin, Neoview Command Interface, and JDBC applications can display data from multiple
client locale characters. Neoview ODBC drivers can display only data that matches the client
locale characters and replaces all other characters (by default, with question marks).
An example of a multiple client locale environment is one where every client workstation, no
matter its local character set encoding, can access Neoview DB Admin or a customer query
application and display SQL table and column names in every supported client locale character
encoding. On the other hand, if every client workstation only displays table and column names
that are encoded in its own current encoding and shows question marks for all other character
set data, multiple client locales are not supported.
To display different languages from multiple client locales, all those languages must be installed
on every client locale.
Neoview Character Set Configurations
For this Neoview release, one of these three Neoview character set configurations must be selected
and configured on each Neoview platform:
• ISO88591 configuration
• SJIS configuration
• Unicode configuration
Your HP support provider can work with you to identify the correct configuration for your
database environment. For information about how to select the correct configuration for your
Neoview platform, see Table 2-1 (page 21).
Table 1-3 (page 17) describes the key features, behaviors, and limitations of the three Neoview
character set configurations for this Neoview release.
16 Introduction to Neoview Character Sets