The HATS user interface and context-sensitive help are provided in these languages:
All the languages are installed in a single product image. National language support is operating-system dependent, therefore the appropriate font and keyboard support for the language you want to use must be installed in the operating system. For example, if you want to use French as the host-session language but do not have the French font and keyboard support installed, you may not be able to display the correct characters.
Language codes are used in different parts of the product to determine which language to present to the user. Refer to Table 11 for the language and language code.
Language | Language Code |
---|---|
Arabic | ar |
Czech | cs |
German | de |
English | en |
Spanish | es |
French | fr |
Hungarian | hu |
Italian | it |
Japanese | ja |
Korean | ko |
Polish | pl |
Brazilian Portuguese | pt_BR |
Russian | ru |
Turkish | tr |
Chinese (Simplified) | zh |
Chinese (Traditional) | zh_TW |
HATS supports the following code pages. You can select the code page for each HATS project when you create the project, and you can modify it later in the project editor.
Code page | Location or usage |
---|---|
037 |
Belgium Brazil Canada Netherlands Portugal United States |
273 |
Austria Germany |
274 |
Belgium (Old) |
275 |
Brazil (Old) |
277 |
Denmark Norway |
278 |
Finland Sweden |
280 |
Italy |
284 |
Spain Latin-America (Spanish) |
285 |
United Kingdom |
297 |
France |
420 |
Arabic Speaking |
424 |
Hebrew (New Code) |
500 |
Multilingual |
803 |
Hebrew (Old Code) |
838 |
Thai |
870 |
Bosnia/Herzegovina Croatia Czech Republic Hungary Poland Romania Slovakia Slovenia |
871 |
Iceland |
875 |
Greece |
924 |
Multilingual ISO Euro |
930 |
Japanese (Katakana) Japan (Katakana Extended) |
933 |
Korea |
937 |
Taiwan (Traditional Chinese) Note: To support accented characters see Using accented characters for code page 937. |
939 |
Japanese (Latin Extended) |
1025 |
Belarus Bulgaria FYR Macedonia Russia Serbia/Montenegro (Cyrillic) |
1026 |
Turkey |
1047 |
Open Edition |
1112 |
Latvia Lithuania |
1122 |
Estonia |
1123 |
Ukraine |
1137 |
Hindi |
1140 |
Belgium Euro Brazil Euro Canada Euro Netherlands Euro Portugal Euro United States Euro |
1141 |
Austria Euro Germany Euro |
1142 |
Denmark Euro Norway Euro |
1143 |
Finland Euro Sweden Euro |
1144 |
Italy Euro |
1145 |
Latin-America Euro (Spanish) Spain Euro |
1146 |
United Kingdom Euro |
1147 |
France Euro |
1148 |
Multilingual Euro |
1149 |
Iceland Euro |
1153 |
Bosnia/Herzegovina Euro Croatia Euro Czech Republic Euro Hungary Euro Poland Euro Romania Euro Slovakia Euro Slovenia Euro |
1154 |
Belarus Euro Bulgaria Euro FYR Macedonia Euro Russia Euro Serbia/Montenegro (Cyrillic) Euro |
1155 |
Turkey Euro |
1156 |
Latvia Euro Lithuania Euro |
1157 |
Estonia Euro |
1158 |
Ukraine Euro |
1160 |
Thai Euro |
1166 |
Kazakhstan Euro |
1364 |
Korea Euro |
1371 |
Taiwan (Traditional Chinese) Euro |
1388 |
PRC (Simplified Chinese Extended; GB18030) |
1390 |
Japanese (Katakana Unicode Extended) |
1399 |
Japanese (Latin Unicode Extended) |
The character set used in HATS JSPs, such as HATS transformations and templates, must match the encoding configured in the user's browser, as well as the encoding specified in the application server. HATS applications create JSPs in all locales using the UTF-8 character set.
WebSphere® Application Server has different default encoding settings for different locales. Some double-byte characters and bidirectional language data input might be decoded incorrectly if the encoding setting for that locale is not UTF-8. You must configure the application server on which your HATS application runs to use the same encoding used by the JSP in your HATS application. To configure UTF-8, follow these steps:
The Enable Unicode Data Stream parameter, allows you to configure a connection parameter for 5250 hosts. The unicodeDataStreamEnabled parameter is a parameter on the Advanced tab of the Connection Editor. To add the parameter, go to the Configure optional, advanced connections settings and click the Add button. Select the unicodeDataStreamEnabled parameter from the pull down Name menu and enter the Value. Click OK.
If you use the Traditional Chinese code page 937 for a 5250 connection and want to support the use of accented characters, you must add the advanced connection settings parameter, useAccentedCharacters, and set its value to true on the Advanced tab of the Connection editor. See Advanced for how to add Host On-Demand session parameters. In addition, because the CCSID 937 does not support accented characters, to use this support you must ensure that the CCSID is 65535 on the host. This feature is only supported for 5250 connections.
Following is a list of considerations when using the PRC (Simplified Chinese Extended; GB18030) code page 1388:
There have been host-to-PC code mapping inconsistencies between IBM Personal Communications and Host On-Demand products on a number of DBCS code points when Japanese host code page 1390 or 1399 is used. In Host On-Demand, the UseHodCDRA1399 parameter controls the Unicode remap to correct the inconsistencies. The following table summarizes the mapping for both true and false settings of the UseHodCDRA1399 parameter:
EBCDIC code point |
Unicode code point (UseHodCDRA1399=true) |
Unicode code point (UseHodCDRA1399=false) |
---|---|---|
0x4260 | U+FF0D (Fullwidth hyphen-minus) | U+2212 (Minus sign) |
0xE9F3 | U+2212 (Minus sign) | U+FF0D (Fullwidth hyphen-minus) |
0x43A1 | U+FF5E (Fullwidth Tilde) | U+301C (Wave Dash) |
0xE9F4 | U+301C (Wave Dash) | U+FF5E (Fullwidth Tilde) |
0x447C | U+2225 (Parallel To) | U+2016 (Double Vertical Line) |
0xDFE5 | U+2016 (Double Vertical Line) | U+2225 (Parallel To) |
0x444A | U+2015 (Horizontal Bar) | U+2014 (EM Dash) |
0xDDB7 | U+2014 (EM Dash) | U+2015 (Horizontal Bar) |
0x426A | U+FFE4 (Fullwidth Broken Bar) | U+00A6 (Broken Bar) |
0xE9F5 | U+00A6 (Broken Bar) | U+FFE4 (Fullwidth Broken Bar) |
HATS uses the Host On-Demand UseHodCDRA1399 parameter for the same purpose. The HATS default for the UseHodCDRA1399 parameter is false. To set the parameter to true, edit the connection in your HATS project and perform the following steps:
JIS2004, which is a new Japanese national standard coded character set, adds three types of new characters:
When using JIS2004 in your applications, consider the following items:
For HATS Web applications, enable the style setting in each HATS widget, such as the Field Widget, to add the following fonts:
For HATS rich client applications, set the font setting in each HATS widget to the MS Mincho font.
To print JIS2004 characters:
The following table shows the results of specifying different values for the KANJI_CODE session parameter with different pdfpdt files when printing data with JIS2004 characters to an output file (Print-to-File):
Session parameter in pdfpdt file | ASCII text mode (basic_dbcs.pdf) | Other supported printers (esc_*.pdf, ibm*.pdf, lips*.pdf, etc.) |
---|---|---|
KANJI_CODE=SHIFT_JIS | Not applicable since surrogate pairs can not be stored in a native PC file. | The output is saved to a native PC file and font images (binary data) for JIS2004 characters and UDA characters are stored in this file. |
KANJI_CODE=UNICODE | The output is saved to a Unicode file; surrogate pairs and UDA characters are stored in UCS-2. | Not applicable since a PC printer does not accept Unicode data. |
In addition, you should also configure the session parameters printerMimeType and printSaveAsExtension properly when printing to a file:
Setting | Session parameter in pdfpdt file | Session parameter printerMimeType in HATS | Session parameter printSaveAsExtension in HATS | Results |
---|---|---|---|---|
Setting for further printing | KANJI_CODE=SHIFT_JIS | application/octet-stream | .bin | A native PC file with binary data. |
Setting for ASCII text mode | KANJI_CODE=UNICODE | text/plain | .txt | A UCS-2 file. |
For more information see Defining print support for your project and Printing.
To disable JIS2004 support for a connection using code pages 1390 and 1399, perform the following steps:
HATS support for Host On-Demand custom tables allows you to remap the user's keyboard and display characters by customizing the host to PC code page conversion tables. A custom table file can contain any number of tables, in any combination of keyboard and display tables. Keyboard tables remap the user's keyboard characters as input customized for a host application. Display tables remap host display characters into screen output customized for the user.
A sample custom table file, CustomTableExample.txt, is located in the <RationalSDP_install_directory>\hats\customtables directory. The file format is similar to that of Java properties files. Lines that start with # are comments, and variables shown as n and N are hexadecimal values. The following example shows the format of the sample custom table file.
##### Start of file
# Map SBCS Local nn to SBCS EBCDIC NN in keyboard table
sbcs.keyboard.0xnn=0xNN
# Map DBCS Unicode nnnn to DBCS EBCDIC NNNN in keyboard table
dbcs.keyboard.0xnnnn=0xNNNN
...
# Map SBCS EBCDIC NN to SBCS local nn in display table
sbcs.display.0xNN=0xnn
# Map DBCS EBCDIC NNNN to DBCS Unicode nnnn in display table
dbcs.display.0xNNNN=0xnnnn
...
##### End of file
To enable the use of custom tables in your project:
There are several ways to replace characters in HATS. Character replacement by these functions occurs in the following order:
For example, if you use custom table support to change a display character, and text replacement is defined to change the same character, that character does not exist when text replacement occurs.