From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Setting file-name/process coding system from LANG
Date: Sat, 16 Oct 2004 09:53:01 -0400 [thread overview]
Message-ID: <E1CIozV-00037e-K4@fencepost.gnu.org> (raw)
In-Reply-To: <buo655cercn.fsf@mctpc71.ucom.lsi.nec.co.jp> (message from Miles Bader on Fri, 15 Oct 2004 09:51:20 +0900)
Yes -- and in fact it _already_ does this in Emacs.
The problem is that setting the Emacs language-environment (with
`set-language-environment') _overrides_ the initial settings made based on
LANG. That's wrong in this case, I think.
So you're suggesting that set-language-environment simply not change
these settings? That might be ok; however, in other cases
we might want different behavior.
What precisely are these settings?
BTW, another possibly related issue is that if I start `emacs -q' with
LANG=ja_JP, then the language-environment is automatically set to
"Japanese" -- great! But if I start `emacs -q' with LANG=ja_JP.utf8, then
the language environment is set to "utf-8", and that doesn't make much
sense to me -- indeed the whole concept of a "utf-8 language environment"
seems kind of weird. In this case I think it should instead (1) set the
language-environt to "Japanese", and then (2) set the various I/O encodings
to be `utf-8'.
Handa, what do you think?
next prev parent reply other threads:[~2004-10-16 13:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 8:44 Setting file-name/process coding system from LANG Miles Bader
2004-10-15 0:25 ` Richard Stallman
2004-10-15 0:51 ` Miles Bader
2004-10-16 13:53 ` Richard Stallman [this message]
2004-10-17 0:14 ` Miles Bader
2004-10-25 13:13 ` Richard Stallman
2004-10-18 13:04 ` Kenichi Handa
2004-10-19 6:13 ` Richard Stallman
2004-10-19 13:13 ` Kenichi Handa
2004-10-19 13:51 ` Stefan Monnier
2004-10-20 6:02 ` Kenichi Handa
2004-10-20 10:34 ` Richard Stallman
2004-10-19 21:51 ` Miles Bader
2004-10-20 6:21 ` Kenichi Handa
2004-10-20 8:50 ` Miles Bader
2004-10-20 13:02 ` Stefan Monnier
2004-10-20 10:34 ` Richard 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1CIozV-00037e-K4@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.