From: Kenichi Handa <handa@m17n.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Setting file-name/process coding system from LANG
Date: Wed, 20 Oct 2004 15:21:54 +0900 (JST) [thread overview]
Message-ID: <200410200621.PAA29245@etlken.m17n.org> (raw)
In-Reply-To: <20041019215111.GA9395@fencepost> (message from Miles Bader on Tue, 19 Oct 2004 17:51:11 -0400)
In article <20041019215111.GA9395@fencepost>, Miles Bader <miles@gnu.org> writes:
> On Tue, Oct 19, 2004 at 10:13:53PM +0900, Kenichi Handa wrote:
>> > When Emacs sees LANG=ja_JP.utf8, surely it can select the Japanese
>> > language environment, then do something else to cause use of UTF8.
>> > Surely it can do this without having an explicit language environment
>> > for the combination of the two.
>>
>> Then a user can't recover that original setting when he once
>> switch to, e.g., Latin-1. Just switching back to Japanese
>> can't setup coding systems for utf8.
> Why can't we do what I suggested earlier, and set `file-name-coding-system'
> (and presumably some analogue for process I/O and terminal-coding-system)
> instead of `default-file-name-coding-system' from the "utf8" portion of LANG?
If it always sets file-name-coding-system, there's no need
of having default-file-name-coding-system. And, that means
that even if one changes to latin-1 lang. env.,
file-name-coding-system is still utf-8. Is it ok? Am I
misunderstanding something?
> Then `set-language-environment' could set `default-file-name-coding-system'
> but it wouldn't actually have any effect -- which at least in this
> circumstance seems correct. Other language-environment settings (like the
> tutorial language etc) would have the proper effect.
>> Another problem is the case of LANG=zh_CN.utf8. Currently
>> we don't have Chinese lang. env. We only have Chinese-GB,
>> Chinese-EUC-TW, Chinese-BIG5, Chinese-CNS. Which one to
>> use?
> Presumably whichever one best matches the "country" portion of LANG.
It seems to be difficult.
% locale -a|grep zh
shows these:
zh_CN
zh_CN.gb18030
zh_CN.gb2312
zh_CN.gbk
zh_CN.utf8
zh_HK
zh_HK.big5hkscs
zh_HK.utf8
zh_SG
zh_SG.gb2312
zh_SG.gbk
zh_TW
zh_TW.big5
zh_TW.euctw
zh_TW.utf8
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2004-10-20 6:21 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
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 [this message]
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
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=200410200621.PAA29245@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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).