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

Re: XTerm and ISO-2022

To: linux-utf8@xxxxxxxxxxxx
Subject: Re: XTerm and ISO-2022
From: Marcin 'Qrczak' Kowalczyk <mk167280@xxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 2 Feb 2001 16:08:30 +0100 (CET)
In-reply-to: <873ddxta5e.wl@surfchem0.riken.go.jp>
Reply-to: linux-utf8@xxxxxxxxxxxx
Sender: owner-linux-utf8@xxxxxxxxxxxx

On Fri, 2 Feb 2001, Tomohiro KUBOTA wrote:

> | And more, the advantage of ISO-2022 which I wrote above would be
> | lost if ISO-2022 is used only under ISO-2022 locale.  (The point
> | of this idea is that ISO-2022 can co-exist with any other encodings.

IMHO ISO-2022 is too horribly designed to push its idea further. I am
against making the terminal interface so complex. If ISO-2022 is used as
someone's private locale, then OK, it can be handled in iconv. But it's
a bad framework to base other things on. Please keep as far from ISO-2022
as possible.

-- 
Marcin 'Qrczak' Kowalczyk

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

References:
- XTerm and ISO-2022
  - From: Tomohiro KUBOTA

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