unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: jorussel@cisco.com, emacs-devel@gnu.org, drew.adams@oracle.com,
	jasonr@gnu.org
Subject: Re: FW: Emacs non-ascii characters
Date: Sat, 26 Nov 2005 16:46:45 +0900	[thread overview]
Message-ID: <E1Efulh-0000h9-00@etlken> (raw)
In-Reply-To: <E1EfrbE-0003zu-R7@fencepost.gnu.org> (rms@gnu.org)

In article <E1EfrbE-0003zu-R7@fencepost.gnu.org>, "Richard M. Stallman" <rms@gnu.org> writes:

>       But if the
>     locale is "en_US", emacs starts with "Latin-1" lang. env. because
>     of this entry.

> I don't understand why that was done,
> since this comment is not very clear.

> 	;; Users who specify "en" explicitly typically want Latin-1, not ASCII.
> 	;; That's actually what the GNU locales define, modulo things like
> 	;; en_IN -- fx.

I don't the wording "modulo things like en_IN".  But, I
think he wanted to indicate this data in
/usr/share/i18n/SUPPORTED.

en_US ISO-8859-1
en_US.UTF-8 UTF-8
en_IN UTF-8

It says that in en_US locale, the encoding iso-8859-1 is
supported, but, in en_US.UTF-8 and en_IN, the encoding UTF-8
is supported.

So, I think, in en_US locale, setting the default coding
system to iso-8859-1 is the right thing.  Currently, we do
that by setting "Latin-1" lang. env.  But that sets
default-input-method to latin-1-prefix, thus C-\
automatically activates it.

> but I also don't see why we would want to change it.

By the change, emacs started under en_US locale is put in
"English" lang. env. (thus default-input-method is not set)
but the default conding systems are still set to iso-8859-1.

---
Kenichi Handa
handa@m17n.org

  reply	other threads:[~2005-11-26  7:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 19:26 FW: Emacs non-ascii characters Drew Adams
2005-11-21 19:40 ` Henrik Enberg
2005-11-21 22:09 ` Eli Zaretskii
2005-11-21 22:24   ` Drew Adams
2005-11-21 23:20     ` Jason Rumney
2005-11-21 23:27       ` Drew Adams
2005-11-21 23:36         ` John Russell (jorussel)
2005-11-22  0:38         ` David Kastrup
2005-11-25  7:37       ` Kenichi Handa
2005-11-25 10:14         ` Jason Rumney
2005-11-25 14:37           ` Aidan Kehoe
2005-11-25 14:51             ` Jason Rumney
2005-11-25 22:49               ` Aidan Kehoe
2005-11-26  4:23         ` Richard M. Stallman
2005-11-26  7:46           ` Kenichi Handa [this message]
2005-11-26  8:20             ` Kenichi Handa
2005-11-26  9:33               ` David Kastrup
2005-11-26  9:04             ` Eli Zaretskii
2005-11-27  0:31             ` Richard M. Stallman
2005-12-05  7:40               ` Kenichi Handa
2005-11-21 22:27   ` Paul Pogonyshev
2005-11-21 22:29     ` Drew Adams
2005-11-21 22:58       ` Paul Pogonyshev
2005-11-21 23:14 ` Jason Rumney
2005-11-25  8:13   ` Miles Bader
2005-11-22  2:21 ` Richard M. Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Efulh-0000h9-00@etlken \
    --to=handa@m17n.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=jorussel@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).