Supported data code pages
Table 1 lists the data code pages that Rational® ClearQuest® supports and the languages associated with them.
ClearQuest supports the UTF-8 (8-bit Unicode Transformation Format) code page for the DB2® and Oracle database sets. This means that ClearQuest supports multilingual data storage for characters from different languages. There are some practical limitations to using UTF-8 as the ClearQuest data code page. See Supported vendor database character sets for details.
For SQL Server, ClearQuest does not support a Unicode code page. This means that ClearQuest can only support storing characters in a SQL Server database that are from one character set. Rational ClearQuest does not support multilingual data storage for SQL Server from different character sets.
Code page | Languages |
---|---|
65001 (UTF-8) | Any except bidirectional and complex script languages |
20127 (US_ASCII) | English |
Safe Shift-JIS (60932) | Japanese |
932 | Japanese |
936 | Simplified Chinese |
949 | Korean |
950 | Traditional Chinese |
1250 (Eastern Europe) | Czech, Croatian, Hungarian, Polish, Romanian, Slovak, Slovenian, Albanian |
1251 (Cyrillic) | Belarussian, Bulgarian, Macedonian, Russian, Serbian, Ukrainian |
1252 (Western Europe) | Spanish, Danish, German, English, French, Italian, Norwegian, Dutch, Portuguese, Swedish, |
1253 | Greek |
1254 | Turkish |
1255 | Hebrew |
1257 (Baltic) | Estonian, Lithuanian, Latvian |
Special considerations for individual data code pages
Each data code page corresponds to a Microsoft code page. A small number of characters from the Microsoft Windows code pages are excluded from the corresponding ClearQuest data code pages to support correct operations across all supported vendor databases.
In addition, the following sections describe special considerations applying to particular data code pages.
Support for data code page 1255 (Hebrew)
- Hebrew can be used as labels on forms.
- Hebrew-only strings can be entered and displayed in any field that accepts string data.
- A mixture of Hebrew and ASCII can entered and displayed in multiline text fields, provided that Hebrew and ASCII appear on different lines and are not mixed on the same line.
- Hebrew can be displayed in the results grid.
- Hebrew can be used in filters. However, only one language can be used to filter each field. A mixture of Hebrew and ASCII cannot be used to filter a single field.
Using data code page 60932 (Japanese safe Shift-JIS)
Some schema repositories created with a previous version of ClearQuest run against vendor databases that use the EUC-JP encoded vendor database character set. EUC-JP is the standard code page for Linux and the UNIX system in Japanese, but it can also be used in some Japanese databases on Windows. To take advantage of extended code page support in version 7.0 and later, support for data code page 60932, also called safe Shift-JIS, is available.
Data code page 60932 is a ClearQuest data code page that consists of the characters in common to Japanese code page 932 (the standard for Windows) and EUC-JP. This data code page blocks input of any characters that cannot be safely converted to EUC-JP. It is used to ensure data integrity when storing Japanese data in a database server on the UNIX system and Linux that uses the EUC-JP vendor database character set.