unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: LEE Sau Dan <danlee@informatik.uni-freiburg.de>
Subject: Re: recommended Chinese input methods in emacs?
Date: 14 Jun 2004 14:38:15 +0200	[thread overview]
Message-ID: <m3k6ya5n7s.fsf@mika.informatik.uni-freiburg.de> (raw)
In-Reply-To: 87aczcwdej.fsf@osu.edu

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-7, Size: 2499 bytes --]

>>>>> "Benjamin" == Benjamin Rutt <rutt.4+news@osu.edu> writes:

    Benjamin> The version of GNU Emacs I'm running comes with the
    Benjamin> following chinese input methods:

    Benjamin> chinese-4corner chinese-array30 chinese-b5-quick
    Benjamin> chinese-b5-tsangchi chinese-ccdospy chinese-cns-quick
    Benjamin> chinese-cns-tsangchi chinese-ctlau chinese-ctlaub
    Benjamin> chinese-ecdict chinese-etzy chinese-punct
    Benjamin> chinese-punct-b5 chinese-py chinese-py-b5
    Benjamin> chinese-py-punct chinese-py-punct-b5 chinese-qj
    Benjamin> chinese-qj-b5 chinese-sw chinese-tonepy
    Benjamin> chinese-tonepy-punct chinese-ziranma chinese-zozy

    Benjamin> Can someone recommend one or two of these input methods

It's up  to you, your own  taste and personal  preference.  That's why
there are so many there to choose from.


    Benjamin> as being either the easiest one to learn 

Well...  if  you speak  Mandarin (or something  close) as  your mother
tongue  and  you have  learnt  Pinyin,  then chinese-tonepy-punct  and
chinese-py-punct-b5  would be  the easiest.   If you  speak Cantonese,
then chinese-ctlaub and chinese-ctlau would be easy IF you're familiar
with the C.T. Lau Romanization of Cantonese.


    Benjamin> and/or the one that leads to the highest productivity in
    Benjamin> the long run, for a native Chinese speaker?

Cangjie (for  traditional characters).   It is ubiquitous  on computer
systems  supporting   traditional  characters  (Big5   encoding).   It
requires some training.  Once trained, you can easily get to 20+ chars
per minute.   Professional typists can  reach 40 or 60.   Some wizards
are  reported to  type  at 200  chars  per minute!   This is  possible
because Canjie  is shape-based, and  hence doesn't need to  go through
the  shape->sound->code  process  when   one  types.   It's  a  direct
shape->code translation.  So, touch-typing is possible.

If  you want  some speed  but  don't want  to spend  time on  training
yourself, try  chinese-4corner.  It is shape-based, too.   So, you can
enter characters  even when you don't  know how to  pronounce it.  You
need to  learn the "4-corner" rules, which  is just a 4  x 7 character
poem.  Quite easy to learn.  Reasonably fast (not very fast due to the
high frequency of code collision).



-- 
Lee Sau Dan                     +Z05biGVm-                          ~{@nJX6X~}

E-mail: danlee@informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee

      parent reply	other threads:[~2004-06-14 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 22:54 recommended Chinese input methods in emacs? Benjamin Rutt
2004-06-10  0:34 ` William Xuuu
2004-06-14 12:38 ` LEE Sau Dan [this message]

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=m3k6ya5n7s.fsf@mika.informatik.uni-freiburg.de \
    --to=danlee@informatik.uni-freiburg.de \
    /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).