[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ISO-2022

To: linux-utf8@xxxxxxxxxxxx
Subject: Re: ISO-2022
From: Bruno Haible <haible@xxxxxxx>
Date: Fri, 2 Feb 2001 14:46:59 +0100 (CET)
In-reply-to: <87elxh97k1.wl@surfchem0.riken.go.jp>
References: <87g0hyjpyd.wl@surfchem0.riken.go.jp> <E14OPRS-0004IW-00@wisbech.cl.cam.ac.uk> <87elxh97k1.wl@surfchem0.riken.go.jp>
Reply-to: linux-utf8@xxxxxxxxxxxx
Sender: owner-linux-utf8@xxxxxxxxxxxx

Tomohiro KUBOTA writes:

> We can use Japanese without ISO-2022 support ...
> I want a few infrastructure softwares such as XTerm to support it
> (so that ISO-2022-enabled software can run on them)

If you say Japanese terminals are usable without ISO-2022 support, why
do you want XTerm to support ISO-2022? This would only lead to more
Japanese software that does special hacks for supporting this old
ISO-2022. It'd be better if software from Japanese authors would use
standard APIs (mb/wc etc.), so it can be more useful outside Japan.

Take for example w3m, a superb text mode browser. It has special
options for JIS, Shift_JIS, EUC-JP, but nothing which works with all
encodings.

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

Follow-Ups:
- XTerm and ISO-2022
  - From: Tomohiro KUBOTA

References:
- ISO-2022 (Re: filename encoding (was: ISO-2022))
  - From: Tomohiro KUBOTA
- Re: ISO-2022
  - From: Markus Kuhn
- Re: ISO-2022
  - From: Tomohiro KUBOTA

Prev by Date: Re: filename encoding (was: ISO-2022)
Next by Date: Re: filename encoding (was: ISO-2022)
Previous by thread: Re: ISO-2022
Next by thread: XTerm and ISO-2022
Index(es):
- Date
- Thread