unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Hou, Ruoyu" <phoenixhou@gmail.com>
To: Emacs Mailing List <help-gnu-emacs@gnu.org>
Subject: Questions on charset encoding detection and keyboard layout
Date: Thu, 10 Dec 2009 22:42:11 +0800	[thread overview]
Message-ID: <4B2108C2.8000506@gmail.com> (raw)

Hello,

I am a beginner to emacs and starting to experience some problems on 
multilingual editing. I just hope someone would kindly give me some 
hints. My main platform is NetBSD 5.0.1 running emacs23.1-gtk from pkgsrc.

1. My working environment involves handling documents with major eastern 
Asian characters in different encodings(GB2312, GB18030, BIG5, GBK, 
UTF-8, Shift-JIS, EUC-JP, ISO-2022-JP). My language environment was set 
as UTF-8, because I want all the documents *I create* saved as UTF-8, 
and properly display/edit/save other file in different encodings without 
changing the raw encodings. I noticed that my emacs was not properly 
recognizing documents encoded with euc-jp, so I have to manually set it 
every time I encounter such documents. Is there any configurations I 
could tweak to accurately auto-detect and display the file encodings I 
mentioned above? In most occasions, I don't have any a priori knowledge 
on what the exact encoding is in a given document.

 From the manual I learnt that some encodings are not easily 
distinguishable one another. So I guess the setting would be delicate. 
Some gvim user mentioned that EUC-JP has to be located before GBK in 
encoding list to get appropriate result.

2. I'm using a computer with Japanese keyboard layout(a 84-key notebook 
variant of jp-106). When using emacs in X GUI mode, the language 
conversion keys (<henkan>, <muhenkan>, <hirakana/katakana>, etc.) 
respond perfectly in echo area, so I can bind some key macros to toggle 
Japanese input method. However, when I start emacs -nw in say uxterm, 
those keys are not echoed.

Frankly, I prefer to run emacs in non-GUI mode for faster response on my 
old notebook. I'm wondering if I could also configure those conversion 
keys to work the same as in GUI mode. Do I have to changing any settings 
in X or emacs? Is there anyone experiencing a similar situation?

I have to confess that I do not have much experiences in emacs after 
switching my work platform to open source softwares, and as a somewhat 
busy benchwork biologist I probably missed some homework I should have 
done before asking. I would appreciate any hints or reference readings. 
Thanks for any attention.

Regards,
-- 
Hou, Ruoyu

Laboratory of Reproductive & Stem Cell Biology,
College of Life Science & Biotech.,
Shanghai Jiao Tong University,
Shanghai 200240, P.R.China.




             reply	other threads:[~2009-12-10 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 14:42 Hou, Ruoyu [this message]
2009-12-10 19:03 ` Questions on charset encoding detection and keyboard layout Eli Zaretskii
2009-12-11  5:42   ` Hou, Ruoyu
2009-12-11  8:42     ` Eli Zaretskii
2009-12-11 15:18       ` Kevin Rodgers
2009-12-11 19:51       ` Hou, Ruoyu
2009-12-11 20:54         ` Eli Zaretskii

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=4B2108C2.8000506@gmail.com \
    --to=phoenixhou@gmail.com \
    --cc=help-gnu-emacs@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.
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).