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

B Capabilities and Limitations of Multiple Client Locales in
the Unicode Configuration
This appendix describes the capabilities and limitations imposed on multiple client locales in
the Unicode configuration for this Neoview release.
Table B-1 Capabilities and Limitations for Multiple Client Locales in the Unicode Configuration
Recommended User Actions (If Any)Capabilities and Limitations
Use only character sets that are compatible across all the
client workstations.
All the character sets used by the client workstations must
be compatible.
To be able to view all the characters displayed from
Neoview client applications, make sure the character fonts
associated with all the supported client locale character
encodings have been installed and their code pages are
present on every client workstation.
From Neoview client applications such as Neoview DB
Admin, each client workstation can display the characters
of every client locale language for which the code pages
are present and all the associated fonts have been installed
on the workstation.
Make sure the fonts associated with all the supported
character sets have been installed and defined on every
client workstation.
From each client workstation, Unicode-aware Neoview
client applications such as Neoview DB Admin, Neoview
Command Interface, and the Neoview JDBC driver can
accept, display, and process those character sets that are
installed and defined on that workstation.
The Unicode configuration supports the use of SQL
identifiers of any character set type in table and column
names when they are entered and retrieved from
Unicode-aware Neoview client applications such as
Neoview DB Admin, Neoview Command Interface, and
the Neoview JDBC driver. Neoview ODBC drivers return
SQL identifiers and character data in the client locale
character encoding. Data that is not compatible with the
client locale character encoding is replaced with and
displayed as replacement characters (question marks by
default).
Neoview ODBC drivers, which are not Unicode aware,
automatically translate all client locale character encoding
sent to the Neoview database to UCS2 encoding and
converts retrieved UCS2 database encoding to the client
locale character encoding.
Use a Neoview JDBC driver-connected query application
to display data in all the encodings that are compatible
with the current character set on the client workstation.
From a client workstation, Neoview ODBC
driver-connected query applications display and return
only columns and user data that are encoded in the
current character set of the workstation.
47