Re: Adjusting terminal via ISO 2022 to locale encoding

[Jungshik Shin]

On Tue, 15 May 2001, Jungshik Shin wrote:
> > Jungshik Shin wrote on 2001-05-15 16:41 UTC:

> > > However, EUC-JP, EUC-CN, and EUC-KR are as widely used as
> > > ISO-8859-x and there ARE ISO-2022 ESC seq. to activate these encodings.

>
>    EUC-KR              : "\033(B\033$)C"
>                          G0: US-ASCII, G1: KS C 5601-1987 (now KS X 1001)
>    EUC-CN (GB 2312-80) : "\033(B\033$)A"
>                          G0: US-ASCII, G1: GB 2312-80

  I didn't check ISO 2022, but am pretty sure that by default
(i.e. without explicit announcement) G0 and G1 are invoked on GL
(0x21-0x7e) and GR (0xa1-0xfe) respectively. However, I may be wrong.

>   In case of EUC-JP, I may have been wrong. I don't see a way to take
> care of JIS X 0212.

  My memory is certainly faltering. For sure, there's a way to announce
EUC-JP.

   EUC-JP   : "\033(B\033$)B\033$+D\033\040|"
             G0: US-ASCII, G1: JIS X 0208  G3: JIS X 0212

  -   In EUC-JP, single shift (SS2 and SS3) are used to invoke
      the following *single* one (half-width katana : G2) or two byte (G3)
      character onto GR. "\033\040|" announces that
      G2 and G3 are invoked on GR rather than GL when following
      SS2/SS3.

  -  G2 should be half-width katakana, but I don't know
     if there's any registered character set for that with esc.
     sequence.

  -  G1 designation for JIS X 0208 may have to be
     "\033\046@\033$)B" instead of "\033$)B"

  Jungshik Shin

-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/