Sun Microsystems, Inc.
spacerspacer
spacer www.sun.com docs.sun.com |
spacer
black dot
 
 
4.  Supported Asian Locales Japanese Localization Japanese Input Systems  Previous   Contents   Next 
   
 

Terminal Setting for Japanese Terminals

Using Japanese locales on a character-based terminal (TTY) requires that you use terminal settings to make line editing work correctly.

  • If your terminal is a CDE Terminal emulator (dtterm), use stty(1) with argument -defeucw in any Japanese locale (ja, ja_JP.PCK, or ja_JP.UTF-8). An example in locale ja is:
    % setenv LANG ja
    % stty defeucw 	

  • If your terminal is not a CDE Terminal emulator, but the codeset of your terminal is the same as that of the current locale, use stty(1) with argument -defeucw.

  • If your terminal's codeset doesn't match that of the current locale, use setterm(1) to enable code conversion. For example, if you are in locale ja but your terminal requires PCK (Shift_JIS code), specify:
    % setenv LANG ja 
    % setterm -x PCK 		

    See the setterm(3CURSES) man page for details.

Japanese iconv Module

Several Japanese codeset conversions are supported with iconv(1) and iconv(3). See the iconv_ja(5) man page for details.

User-Defined Character Support

The user-defined character utility sdtudctool handles both outline (Type1) and bitmap (PCF) fonts. Some utilities are also available to migrate the UDC fonts that were created by old utilities in prior releases, such as fontedit, type3creator, and fontmanager.

Differences Between Partial and Full Locales

The following components are only available in the Japanese full locale environment with the Language CD:

  • Translated message, help, and man pages

  • Wnn6 Japanese input system

  • Japanese Solaris 1.x BCP support

  • Mincho (min*) typeface bitmap fonts

  • JIS X 0212 Type1 fonts for printing

  • Japanese-specific dumb printer and jpostprint support

  • Legacy Japanese utilities such as kanji(1)

Korean Localization

In December 1995, the Korean government announced a standard Korean codeset, KS X 1005-1, which is based on ISO 10646-1/Unicode 2.0.

The ISO-10646 character set uses two universal character sets:

  • UCS-2. Universal Character Set (two-byte form)

  • UCS-4. Universal Character Set (four-byte form).

The ISO-10646 character set cannot be used directly on IBM PC-based operating systems. For example, the kernel and many other modules of the Solaris operating environment interpret certain byte values as control instructions, such as a null character (0x00) in any string. The ISO-10646 character set can be encoded with any bit combinations in the first or subsequent bytes. The ISO-10646 characters cannot be freely transmitted through the Solaris system with these limitations.

In order to establish a migration path, the ISO-10646 character set defines the UCS Transformation Format (UTF), which recodes the ISO-10646 characters without using C0 controls (0x00..0x1F), C1 controls (0x80..0x9F), space (0x20), and DEL (0x7F).

The ko.UTF-8 is a Solaris locale to support KS X 1005-1, the Korean standard codeset. This locale supports all characters in the previous KS X 1005 and all 11,172 Korean characters. Korean UTF-8 supports the Korean language-related ISO-10646 characters and fonts. Because ISO-10646 covers all characters in the world, all of the various input methods and fonts are supplied so that you can input and output any character in any language. Before Universal UTF/UCS becomes available, Korean UTF-8 supports the ISO-10646 code subset that is related to Korean characters as well as all other characters in the previous Korean standard codeset, and extended ASCII.

In the ko locale, the EUC scheme is used to encode KS X 1001. The ko.UTF-8 locale supports the KS X 1005-1/Unicode 2.0 codeset, which is a superset of KS X 1001. These two locales look the same to the end user, but the internal character encoding is different. The Korean Solaris product supports the following input methods:

For the ko locale:

  • Hangul 2-BeolSik (one set of consonants and one set of vowels)

  • Hangul-Hanja conversion

  • Special character

  • Hexadecimal code

For the ko.UTF-8 locale:

  • Hangul 2-BeolSik (one set of consonants and one set of vowels)

  • Hangul-Hanja conversion

  • Special character

  • Hexadecimal code

The following table shows the Korean bitmap fonts for the ko locale.

Table 4-16 Solaris 9 Korean Bitmap Fonts for the ko Locale

Full Family Name

Subfamily

Format

Encoding

Gothic R/B PCF (12,14,16,18,20,24) KS X 1001 
Graphic R/B PCF (12,14,16,18,20,24) KS X 1001 
Haeso R/B PCF (12,14,16,18,20,24) KS X 1001 
Kodig R/B PCF (12,14,16,18,20,24) KS X 1001 
Myeongijo R/B PCF (12,14,16,18,20,24) KS X 1001 
Pilki R/B PCF (12,14,16,18,20,24) KS X 1001 
Round gothic R/B PCF (12,14,16,18,20,24) KS X 1001 

The following table shows the Korean bitmap fonts for the ko.UTF-8 locale.

Table 4-17 Solaris 9 Korean Bitmap Fonts for the ko.UTF-8 Locale

Full Family Name

Subfamily

Format

Encoding

Gothic R/B PCF (12,14,16,18,20,24) KS X 1001 (Johap)
Graphic R/B PCF (12,14,16,18,20,24) KS X 1001 (Johap)
Haeso R/B PCF (12,14,16,18,20,24) KS X 1001 (Johap)
Kodig R/B PCF (12,14,16,18,20,24) KS X 1001 (Johap)
Myeongijo R/B PCF (12,14,16,18,20,24) KS X 1001 (Johap)
Pilki R/B PCF (12,14,16,18,20,24) KS X 1001 (Johap)
 
 
 
  Previous   Contents   Next