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

Re: ISO 2022 versus UTF-8 autodetection heuristics

To: linux-utf8@nl.linux.org
Subject: Re: ISO 2022 versus UTF-8 autodetection heuristics
From: hpa@transmeta.com (H. Peter Anvin)
Date: 3 Nov 1999 23:54:20 GMT
Copyright: Copyright 1999 H. Peter Anvin - All Rights Reserved
Disclaimer: Not speaking for Transmeta in any way, shape, or form.
Organization: Transmeta Corporation, Santa Clara CA
References: <Bram@moolenaar.net> <199911032229.RAA15846@shell.clark.net>
Reply-To: linux-utf8@nl.linux.org
Sender: owner-linux-utf8@nl.linux.org

Followup to:  <199911032229.RAA15846@shell.clark.net>
By author:    "T.E.Dickey" <dickey@clark.net>
In newsgroup: linux.utf8
> 
> It's the terminal emulator, not the editor or other application that
> has to deal with the %G.
> 

Not if it is stored in the file.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/

Follow-Ups:
- Re: ISO 2022
  - From: Markus Kuhn <Markus.Kuhn@cl.cam.ac.uk>

References:
- Re: ISO 2022 versus UTF-8 autodetection heuristics
  - From: "T.E.Dickey" <dickey@clark.net>

Prev by Date: Re: ISO 2022 versus UTF-8 autodetection heuristics
Next by Date: Re: ISO 2022 and termcap ballast
Prev by thread: Re: ISO 2022 versus UTF-8 autodetection heuristics
Next by thread: Re: ISO 2022
Index(es):
- Date
- Thread