[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: David Starner <dstarner98@xxxxxxxxxxxxx>
Date: Fri, 2 Feb 2001 12:51:17 -0600
In-reply-to: <Pine.LNX.4.21.0102021808000.1049-100000@janus.arrow>; from robert@suse.co.uk on Fri, Feb 02, 2001 at 06:11:40PM +0000
References: <87k879hxbk.wl@surfchem0.riken.go.jp> <Pine.LNX.4.21.0102021808000.1049-100000@janus.arrow>
Reply-to: linux-utf8@xxxxxxxxxxxx
Sender: owner-linux-utf8@xxxxxxxxxxxx
User-agent: Mutt/1.3.12i

On Fri, Feb 02, 2001 at 06:11:40PM +0000, Robert Brady wrote:
> That doesn't sound like a very convincing reason, you can just stuff all
> output through a 2022 -> UTF-8 converter.  Don't see any reason for this
> to be in the terminal itself...

Does anyone know of a general 2022 -> UTF-8 converter? 

-- 
David Starner - dstarner98@xxxxxxxxxxxxx
Pointless website: http://dvdeug.dhis.org
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/

Follow-Ups:
- Re: XTerm and ISO-2022
  - From: Markus Kuhn
- Re: XTerm and ISO-2022
  - From: Bruno Haible

References:
- Re: XTerm and ISO-2022
  - From: Tomohiro KUBOTA
- Re: XTerm and ISO-2022
  - From: Robert Brady

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