Unicode support for i5/OS and OS/400 using Coded Character Set Identifiers
Configuring the font on the client
General information
In a 5250 Display session, Z and I Emulator for Web supports the display of Unicode data located in fields tagged with Coded Character Set Identifiers (CCSIDs). The Enable Unicode Data Stream option in the 5250 Display session configuration window must be set to Yes (see ENPTUI).
Z and I Emulator for Web does not support this feature in a 5250 Printer session.
Z and I Emulator for Web supports the following CCSIDs:
- 13488 (hexadecimal 0x34B0)
- 17584 (hexadecimal 0x44B0)
Z and I Emulator for Web returns a sense code of 0x10050155 in response to any other CCSID.
Host requirements
The iSeries host must be running one of the following levels of i5/OS or OS/400:
- OS/400 V5R2 with an appropriate manufacturing refresh (see the readme file for details).
- i5/OS or OS/400 V5R3 or higher.
Client workstation requirements
The following requirements apply to the client workstation:
-
Java 1 or Java 2
For bidirectional languages the
client workstation must use one of the following:
- A Java 2-enabled browser with the Z and I Emulator for Web client
- Web Start Z and I Emulator for Web client
- A Java 1 browser with the Z and I Emulator for Web client
- A Java 2-enabled browser with the Z and I Emulator for Web client
- Web Start Z and I Emulator for Web client
-
Fonts
- Bidi languages Use the Courier New font that is already installed on the client workstation. For more information see Understanding bidirectional language support (Arabic and Hebrew).
- Other languages The client workstation must be configured to use one of the Monotype Sans Duospace WT fonts. These fonts are IBM WorldType fonts. See Configuring the font on the client.
Limitations
This feature has the following limitations:
- An SBCS session supports only single-width Unicode characters.
- A DBCS session supports both single-width Unicode characters and double-width Unicode characters.
- However, a DBCS session supports only those double-width Unicode characters that occur in the Monotype Sans Duospace WT font file corresponding to the code page that the session is using. For example, a 5250 Display session configured with Japanese code page 930 supports only those double-width Unicode characters that occur in the Monotype Sans Duospace WT J font file (mtsansdj.ttf).
- This feature does not support the Hindi and Thai code pages.
- This feature does not imply support for GB18030 Phase 2.
- This feature does not support any combining characters in CCSID-based entry field and output data.
- This feature does not support Language Tags (Plane 14) of UTF-16, because Z and I Emulator for Web does not support multiple fonts within one session.
- This feature does not support Tamil and Teluga Unicode characters.
- This feature does not support Tibetan and Mongolian Unicode characters.
- This feature does not support surrogate Unicode characters. These characters are accepted but are displayed incorrectly by Java.
Programming information
Configuring the font on the client
If you are using a Java 2-enabled browser and the IBM Java 2 plug-in
If you are using a Java 2-enabled browser and the Sun Java 2 plug-in
Obtaining the font file
The client workstation must be configured to use one of the IBM WorldType Monotype Sans Duospace WT fonts. The following table shows which font name and font file should be used for each language:
Language: | IBM WorldType font name: | IBM WorldType font file: |
---|---|---|
All SBCS languages and Japanese | Monotype Sans Duospace WT J | mtsansdj.ttf |
Korean | Monotype Sans Duospace WT K | mtsansdk.ttf |
Simplified Chinese | Monotype Sans Duospace WT SC | mtsansds.ttf |
Traditional Chinese | Monotype Sans Duospace WT TC | mtsansdt.ttf |
The next subsections describe how to configure the client workstation to use the font.
If you are using a Java 2-enabled browser and the IBM Java 2 plug-in
If you are using a Java 2-enabled browser (such as Netscape 6.0 or Internet Explorer with a Java 2 plug-in) and the IBM Java 2 plug-in, follow the steps in this section to configure the font on the client.
-
These instructions use the SBCS languages as an example, but the instructions are similar for Japanese, Korean, Simplified Chinese, and Traditional Chinese. However, remember to use the correct Monotype Sans Duospace WT font name and font file for your language, as described in Obtaining the font.
-
In the IBM Java 2 directory, find the font.properties file corresponding to your language:
- For SBCS languages, use
font.properties
- For Japanese, use
font.properties.ja
- For Korean, use
font.properties.ko
- For Simplified Chinese, use
font.properties.zh
- For Traditional Chinese, use
font.properties.zh_TW
c:\Program Files\HCL\Java14
directory, the fully qualified file name for the font.properties file for the SBCS languages isc:\Program Files\HCL\Java14\jre\lib\font.properties
. - For SBCS languages, use
- Modify the font.properties file corresponding to your language as follows:
-
Open the file with an ASCII editor.
-
Find the line beginning with the following characters:
monospaced.0=
-
Modify the group of lines as follows:
- Move the Monotype Sans Duospace WT line to the top.
- Renumber the lines.
monospaced.0=Courier New monospaced.1=Lucida Sans Typewriter Regular monospaced.2=Lucida Sans Regular monospaced.3=Monotype Sans Duospace WT J
These lines should read as follows:monospaced.0=Monotype Sans Duospace WT J monospaced.1=Courier New monospaced.2=Lucida Sans Typewriter Regular monospaced.3=Lucida Sans Regular
-
Make the same changes for the group beginning with
monospaced.italic.0
. -
Make the same changes for the group beginning with
monospaced.bold.0
. -
Make the same changes for the group beginning with
monospaced.bold.italic.0
. -
Close the file.
-
- Restart the browser.
If you are using a Java 2-enabled browser and the Sun Java 2 plug-in
If you are using a Java 2-enabled browser (such as Netscape 6.0 or Internet Explorer with a Java 2 plug-in) and the Sun Java 2 plug-in, follow the steps in this section to configure the font on the client.
-
These instructions use the SBCS languages as an example, but the instructions are similar for Japanese, Korean, Simplified Chinese, and Traditional Chinese. However, remember to use the correct Monotype Sans Duospace WT font name and font file for your language, as described in Obtaining the font.
-
In the Sun Java 2 directory, find the font.properties file corresponding to your language:
- For SBCS languages, use
font.properties
- For Japanese, use
font.properties.ja
- For Korean, use
font.properties.ko
- For Simplified Chinese, use
font.properties.zh
- For Traditional Chinese, use
font.properties.zh_TW
c:\Program Files\Java\j2re1.4.1_02
directory, the fully qualified file name for the font.properties file for the SBCS languages isc:\Program Files\Java\j2re1.4.1_02\lib\font.properties
. - For SBCS languages, use
- Modify the font.properties file corresponding to your language as follows:
-
Open the file with an ASCII editor.
-
Find the line beginning with the following characters:
monospaced.0=
-
Modify the group of lines as follows:
- Add a line at the top for the Monotype Sans Duospace WT font corresponding to the font.properties file. Remember to use the correct Monotype Sans Duospace WT font name for your language, as described in Obtaining the font.
- Renumber the lines.
monospaced.0=Courier New,ANSI_CHARSET monospaced.1=WingDings,SYMBOL_CHARSET monospaced.2=Symbol,SYMBOL_CHARSET
The lines should read as follows:monospaced.0=Monotype Sans Duospace WT J monospaced.1=Courier New,ANSI_CHARSET monospaced.2=WingDings,SYMBOL_CHARSET monospaced.3=Symbol,SYMBOL_CHARSET
-
Make the same changes for the group beginning with
monospaced.italic.0
. -
Make the same changes for the group beginning with
monospaced.bold.0
. -
Make the same changes for the group beginning with
monospaced.bold.italic.0
. - Find the lines that begin with
filename.
- Add the following line anywhere in the list, for example, before the first
line that begins with
filename.:
- If your language is any SBCS language, add the following (the same as
for Japanese):
filename.Monotype_Sans_Duospace_WT_J=mtsansdj.ttf
. - If your language is Japanese, add
filename.Monotype_Sans_Duospace_WT_J=mtsansdj.ttf
. - If your language is Korean, add
filename.Monotype_Sans_Duospace_WT_K=mtsansdk.ttf
. - If your language is Simplified Chinese, add
filename.Monotype_Sans_Duospace_WT_S=mtsansds.ttf
. - If your language is Traditional Chinese, add
filename.Monotype_Sans_Duospace_WT_T=mtsansdt.ttf
.
- If your language is any SBCS language, add the following (the same as
for Japanese):
- Find the line that begins with
exclusion.monospaced.0=
. - Comment out this line by typing a # as the first character of the line, for
example,
#exclusion.monospaced.0=0100-20ab,20ad-f8ff
. -
Close the file.
-
- Restart the browser.
If you are using Netscape 4.x
If you are using Netscape 4.x, then follow the steps in this section to configure the font on the client.
-
These instructions use the SBCS languages as an example, but the instructions are similar for Japanese, Korean, Simplified Chinese, and Traditional Chinese. However, remember to use the correct Monotype Sans Duospace WT font name and font file for your language, as described in Obtaining the font.
-
In the Netscape directory, find the font.properties file corresponding to your language:
- For SBCS languages, use
font.properties
. - For Japanese, use
font.properties.ja
. - For Korean, use
font.properties.ko
. - For Simplified Chinese, use
font.properties.zh
. - For Traditional Chinese, use
font.properties.zh_TW
.
c:\Program Files\Netscape\Communicator
directory, the fully qualified file name for the font.properties file for the SBCS languages isc:\Program Files\Netcape\Communicator\Program\java\classes\font.properties
. - For SBCS languages, use
- Modify the font.properties file corresponding to your language as follows:
-
Open the file with an ASCII editor.
-
Find the line beginning with
monospaced.0=
. -
Modify the group of lines as follows:
- Add a line at the top for the Monotype Sans Duospace WT font corresponding to the font.properties file. Remember to use the correct Monotype Sans Duospace WT font name for your language, as described in Obtaining the font.
- Renumber the lines.
monospaced.0=Courier New,ANSI_CHARSET monospaced.1=Bitstream Cyberbit,DEFAULT_CHARSET monospaced.2=MS Gothic,SHIFTJIS_CHARSET monospaced.3=WingDings,SYMBOL_CHARSET,NEED_CONVERTED monospaced.4=Symbol,SYMBOL_CHARSET,NEED_CONVERTED
The lines should read as follows:monospaced.0=Monotype Sans Duospace WT J monospaced.1=Courier New,ANSI_CHARSET monospaced.2=Bitstream Cyberbit,DEFAULT_CHARSET monospaced.3=MS Gothic,SHIFTJIS_CHARSET monospaced.4=WingDings,SYMBOL_CHARSET,NEED_CONVERTED monospaced.5=Symbol,SYMBOL_CHARSET,NEED_CONVERTED
-
Find the line that begins with
exclusion.monospaced.0=
. - Comment out this line by typing a # as the first character of the line, for
example,
#exclusion.monospaced.0=0100-ffff
. -
Close the file.
-
- Restart the browser.
If you are using Internet Explorer without a Java 2 plug-in
If you are using Internet Explorer and you do not have a Java 2 plug-in installed, then follow the steps in this section to configure the font on the client.
-
These instructions use the SBCS languages as an example, but the instructions are similar for Japanese, Korean, Simplified Chinese, and Traditional Chinese. However, remember to use the correct Monotype Sans Duospace WT font name and font file for your language, as described in Obtaining the font.
-
Find the following key in the Windows Registry:
My Computer\HKEY_LOCAL_MACHINE\Software\Microsoft\Java VM
-
Under this key create the following new key:
Font Alias
-
Under this key create a new String Value with the following Value name:
Courier
-
Modify this String Value to contain the font name for your language. Remember to use the correct Monotype Sans Duospace WT font name for your language, as described in Obtaining the font. For example, for the SBCS languages, modify the String Value to contain the following:
Monotype Sans Duospace WT J
-
Close the registry.
-
Reboot the machine.
- Restart the browser.