Neoview Character Sets Administrator's Guide (R2.3)

2 How to Select the Correct Neoview Character Set
Configuration
Table 2-1 identifies the criteria you should use to identify the correct Neoview Character Set
configuration for your Neoview platform. For professional assistance, contact your HP service
provider.
Table 2-1 Criteria for Selecting the Correct Neoview Character Set Configuration
Additional Considerations
If Your Neoview Platform Environment Meets
Any One of These Conditions or Sets of
Conditions...
Select This
Configuration...
For a summary of the features and
limitations of the ISO88591 configuration for
this release, see Table 1-3 (page 17).
• Migrating Release 2.2 customer wants to
retain the character set behaviors of the
Release 2.2 Neoview platform.
• Want to be able to use any client locale
encoding, including multibyte character
sets, and store the data in that encoding
in ISO88591 columns without any
character mapping or translation.
ISO88591
SJIS users who do not meet these conditions
should select the Unicode configuration if
they do not require JIS collation but do
require support for SQL string functions.
For a summary of the features and
limitations of the SJIS configuration for this
release, see Table 1-3 (page 17).
• Want to provide SJIS characters in SQL
identifiers.
• Is an existing Neoview customer who
already uses the SJIS character set on
Windows PCs with Microsoft codepage
932 (MS932), requires JIS collations, and
uses SJIS characters in table and column
names.
NOTE: If character data that is not fully
compatible with SJIS MS932 encoding is
present in a Release 2.2 database, that
data might not translate successfully in a
migration to the SJIS configuration in the
Release 2.3 environment. For more
information, contact your HP service
provider.
SJIS
Other factors for choosing the Unicode
configuration are:
• Can use any of the character sets
identified in Table 1-3 (page 17).
• Uses the SJIS character set but does not
require JIS collation on their data and will
store the SJIS data in UCS2 columns.
For a summary of the features and
limitations of the Unicode configuration for
this release, see Table 1-3 (page 17).
• Want to use a supported multibyte
character set and need SQL string
function support for those multibyte
characters. Table 1-3 (page 17) identifies
the supported character sets.
• Need to use multiple client locales.
Unicode
Restrictions on Changing the Neoview Character Set Configuration
Once you make any changes to your Neoview Release 2.3 database, the selected Neoview character
set configuration cannot be altered without significant work by HP support personnel and the
customer.
If you need to change the Neoview character set configuration before or after you begin to use
the Release 2.3 database, contact your HP service provider for assistance.
Restrictions on Changing the Neoview Character Set Configuration 21