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

2 Selecting a Neoview Character Set Configuration
This chapter provides this information:
• “Criteria for Selecting a Neoview Character Set Configuration” (page 21)
• “Process for Implementing a Neoview Character Set Configuration” (page 22)
• “Rules for Migrating to Neoview Release 2.4” (page 22)
Criteria for Selecting a 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 support
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).
• Any Neoview Release 2.3 customer with
the ISO88591 configuration who is
migrating to Release 2.4.
• New customer wants 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
For a summary of the features and
limitations of the SJIS configuration for this
release, see Table 1-3 (page 17).
• Any Neoview Release 2.3 customer with
the SJIS configuration who is migrating
to Release 2.4.
• Customer wants to provide SJIS
characters in SQL identifiers.
• A new 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.3 database, that
data might not translate successfully in a
migration to the SJIS configuration in the
Release 2.4 environment. For more
information, contact your HP support
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).
• Any Neoview Release 2.3 customer with
the SJIS configuration who is migrating
to Release 2.4.
• Wants to use multiple client locales.
Unicode
Criteria for Selecting a Neoview Character Set Configuration 21