On Thu, 4 Oct 2001, Thomas E. Dickey wrote:

> On Thu, 4 Oct 2001, Jungshik Shin wrote:
>
> >   By not being effective, do you mean that vim with UTF-8 support would
> > not work even in a console that supports UTF-8? How about connecting
> > to a Linux host using a UTF-8 terminal emulator (e.g. Kermit)?  IMHO,
> > there's certainly a need for making the default vim speak UTF-8.
>
> "want" isn't the same as "need"

  People want it so that there's a need for it.

  Why do you think people need not edit UTF-8 files when connecting to
a remote host with a terminal emulator or in console?  IMHO, UTF-8 is
US-ASCII of the future if not right now. Can you imagine an editor that
cannot speak US-ASCII on a system where US-ASCII is the default encoding
for text?

  Jungshik Shin

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

Reply via email to