Language support

The HATS user interface and context-sensitive help are provided in these languages:

• Arabic
• Brazilian Portuguese
• Chinese (Simplified)
• Chinese (Traditional)
• Czech
• English
• French
• German
• Hungarian
• Italian
• Japanese
• Korean
• Polish
• Russian
• Spanish
• Turkish

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

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.

Code pages

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.

Encoding settings

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:

1. Open the WebSphere Application Server administrative console. If using the local test environment in Rational SDP, in the Servers view, right-click on the server and select Administration > Run administrative console.
2. Log into the administrative console, open the Servers tree in the left navigation panel, and select Application servers.
3. Select the server name to modify.
4. In the right panel, open the Java™ and Process Management tree, select Process Definition, and on the panel that opens next, select Java Virtual Machine .
5. In the Generic JVM arguments section, enter -Dclient.encoding.override=UTF-8.
6. Click the OK button.
7. Select the Save links in the Messages blocks.
8. Log off, and restart WebSphere Application Server.

5250 Unicode support

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.

Using accented characters for code page 937

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.

Using code page 1388 (GB18030)

Following is a list of considerations when using the PRC (Simplified Chinese Extended; GB18030) code page 1388:

• If you add GB18030 characters to a template, you can view them properly in the Source tab, but they might not appear correctly in the Design view of the template editor.
• When working with widgets in screen transformations, GB18030 data might not display in the Rich Page Editor. If not, perform the following steps:
  1. In the Insert Host Component wizard on the Rendering Options panel, click the Widget Settings button.
  2. On the Settings panel, clear the Use project defaults box.
  3. Next to the Style field, click the CSS Style properties button.
  4. Add the GB18030 four-byte supported fonts such as SimSun-18030 to the font family list.
  5. Click OK and Finish, as appropriate, to close the wizard.

Host code mapping for code pages 1390 and 1399

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:

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:

1. Click the Advanced tab.
2. Click Add.
3. From the drop-down list of parameter names, select UseHodCDRA1399.
4. Set the parameter value to true.
5. Click OK.

JIS2004 support

JIS2004, which is a new Japanese national standard coded character set, adds three types of new characters:

1. Normal new characters that were not available before JIS2004 support.
2. Surrogate characters, which are two linked Unicode code points that represent a single character. The two Unicode code points are meaningless if they are separated.
3. Combining characters, which are two Unicode code points combined as one character. The two individual Unicode code points that combine to form a combining character can be displayed separately also.

JIS2004 support considerations and limitations

When using JIS2004 in your applications, consider the following items:

1. JIS2004 is the default Japanese font support with Windows Vista SP1. If you want to continue using JIS90 on the Vista operating system, you can install Microsoft service pack KB927490, which can be downloaded and applied through Windows Update as additional software.
2. To display JIS2004 characters in Windows XP, you must install Microsoft patch KB927489. Even when the patch is installed, you will not be able to insert some JIS2004 characters, such as the surrogate characters, since IME is not supported.
3. The default font setting in HATS does not display JIS2004 characters correctly without some changes to the font settings.

   For HATS Web applications, enable the style setting in each HATS widget, such as the Field Widget, to add the following fonts:

   • MS MinCho
   • MS Gothic
   • Meiryo

   For HATS rich client applications, set the font setting in each HATS widget to the MS Mincho font.

4. When using Internet Explorer V7 and higher, new JIS2004 characters can be supported correctly by setting the fonts as described in the previous item.
5. When using Internet Explorer V6, or when using the preview function in the HATS Toolkit running on Windows XP, some new JIS2004 characters are not displayed correctly at all.
6. Surrogate character support:
   1. In the HATS terminal, when entering JIS2004 characters using IME, the candidate window displays surrogate characters as black squares. However, when the characters are sent to HATS, the HATS terminal displays the surrogate characters correctly.
   2. JIS2004 surrogate characters are not supported for Host On-Demand custom tables.
7. Combining character support:
   1. Windows applications, such as Notepad, and Firefox Version 3 correctly handle JIS2004 combining characters as one character. However, when running HATS rich client applications at runtime, or running HATS Web applications in Internet Explorer, the combining character is handled as two separate characters instead of one character in input fields. The cursor can be placed between the two combining characters.
   2. When running HATS Web applications at runtime in Internet Explorer, if you enter combining characters in the input field, and the Show unprotected Shift Out/Shift In characters as spaces setting in the DBCS section of the Rendering tab is enabled, combining characters become white squares. You can correct the white squares by disabling the setting, or using the Firefox browser.
   3. The HATS PDF print function cannot display combining characters correctly.

JIS2004 support for PDT printing and Print-to-File for 3270E sessions

To print JIS2004 characters:

• For PDT printing, specify a pdfpdt file, such as ibm5577.pdfpdt, and ensure that the parameter KANJI_CODE=SHIFT_JIS is specified.
• For Print-to-File, specify the file encoding using the parameter KANJI_CODE:
  • To save the output as a PC file, dumping the output as a PC file with a font image, set the file encoding to Shift JIS by specifying KANJI_CODE=SHIFT_JIS in the pdfpdt file. The print output is saved as a native PC file that can be used to output the file content to a physical printer.
  • To save the output as an Unicode file, dumping the output as a Unicode file with code points of surrogate pairs, set the file encoding to Unicode by specifying KANJI_CODE=UNICODE in the pdfpdt file. The print output is a UCS-2 file that can be used for further data processing or archiving purposes.

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):

In addition, you should also configure the session parameters printerMimeType and printSaveAsExtension properly when printing to a file:

For more information see Defining print support for your project and Printing.

Disabling JIS2004 support for code pages 1390 and 1399

To disable JIS2004 support for a connection using code pages 1390 and 1399, perform the following steps:

1. Expand your project in the HATS Projects view.
2. Expand the Connections folder
3. Double-click on the connection to open the connection editor.
4. Click the Advanced tab.
5. Under Configure optional, advanced connection settings, click Add.
6. On the Add Parameter panel, enter the following settings.
   1. In the Name field enter enableJIS2004.
   2. In the Value field enter false.
   3. Click OK.

Remapping keyboard and display characters

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:

1. Create a custom table file using the sample as an example and copy it into a folder named, customtables, in the root of the .ear project of your HATS Web application or in the root of the HATS rich client Runtime Extension project for your HATS rich client project. If the customtables folder does not exist, create one.
2. Open your HATS project.
3. Edit the connection by double-clicking the name in the Connections directory.
4. Click the Advanced tab.
5. Click Add.
6. In the Add Parameter dialog, select CustomTable from the drop-down list for Name and enter the name of your custom table file in the Value field.
7. Click OK to exit the Add Parameter dialog.
8. Save your changes to the connection settings.

Priority of character replacement

There are several ways to replace characters in HATS. Character replacement by these functions occurs in the following order:

1. Custom table support
2. UseHodCDRA1399 parameter for DBCS only
3. User Defined Characters (UDCs) for DBCS only
4. Text replacement

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.