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

Re: nl_langinfo(CODESET) again

To: linux-utf8@xxxxxxxxxxxx
Subject: Re: nl_langinfo(CODESET) again
From: Edmund GRIMLEY EVANS <edmundo@xxxxxxxx>
Date: Wed, 24 May 2000 12:10:10 +0100
In-reply-to: <E12uYag-0006L9-00@wisbech.cl.cam.ac.uk>; from Markus.Kuhn@cl.cam.ac.uk on Wed, May 24, 2000 at 11:40:41AM +0100
References: <20000524092316.B25942@daisy.vocalis.com> <E12uYag-0006L9-00@wisbech.cl.cam.ac.uk>
Reply-to: linux-utf8@xxxxxxxxxxxx
Sender: owner-linux-utf8@xxxxxxxxxxxx
User-agent: Mutt/1.3.1i

Markus Kuhn <Markus.Kuhn@xxxxxxxxxxxx>:

>  The prudent thing
> today is clearly to convert to UTF-8 on the sender's side, unless all
> characters fit into US-ASCII or ISO-8859-1.

I think there may still be an occasional local preference for koi8-r
or iso-2022-jp, so I will try to make Mutt configurable in this
respect, with a configuration variable send_charset whose default
value is "us-ascii:iso-8859-1:utf-8", meaning what you suggest, but
some people might want to insert iso-2022-jp or koi8-r in front of
utf-8 if they happen to mostly communicate locally with people using
old software.

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

References:
- nl_langinfo(CODESET) again
  - From: Edmund GRIMLEY EVANS
- Re: nl_langinfo(CODESET) again
  - From: Markus Kuhn

Prev by Date: Re: nl_langinfo(CODESET) again
Next by Date: Re: nl_langinfo(CODESET) again
Previous by thread: Re: nl_langinfo(CODESET) again
Next by thread: Re: nl_langinfo(CODESET) again
Index(es):
- Date
- Thread