unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Lee Sau Dan <danlee@informatik.uni-freiburg.de>
Subject: Re: Chinese characters support
Date: 15 May 2003 10:07:00 +0200	[thread overview]
Message-ID: <m3el31p71h.fsf@mika.informatik.uni-freiburg.de> (raw)
In-Reply-To: ullxb411m.fsf@knight.6test.edu.cn

>>>>> "Robin" == Robin Hu <huxw@knight.6test.edu.cn> writes:

>>>>> "Lee" == Lee Sau Dan <danlee@informatik.uni-freiburg.de> writes:
>>>>> "Charles" == Charles Muller <acmuller@gol.com> writes:

    Lee> Many people using the CJK parts of Emacs only work with the
    Lee> national encodings (Big5, GB, JIS, KSC, etc.)  and in those
    Lee> cases, they Emacs works excellently.

    Robin>     I think you are over-simpilify this problem. ;-( Most
    Robin> CJK characters are not encoded in either Big5 or GB or JIS
    Robin> or KSC, that's why the GB coding standard change from
    Robin> gb2312 to gbk then to gb18030. 

It depends on what you mean  by "most".  Yes, if you include those 10s
of thousnds  of *rare* characters,  then even Unicode can  fall short.
Most Chinese text, for  instance, uses around 5000 distinct characters
only,  of  which  around  1000  accounts  for more  than  90%  of  the
characters in  a text.   Big5 is very  sufficient for normal  use.  If
not, the Chinese  people won't have thrown it away  (e.g. in favour of
Unicode).   Similarly,  Japanese  texts  employ around  3000  distinct
characters, and there  is a government standard list  of characters to
use.  Characters  outside that  list should be  theoretically avoided.
The characters in JIS are based on this set, AFAIK.


    Robin> AFAIK, most chinese characters also cannot be coded within
    Robin> mule, and exists unicode support does not solve this
    Robin> problem.

As long as 99.99% of the characters that I need for Chinese text files
can be encoded in Big5 and emacs-mule, what's the problem?


    Robin>     Of course, emacs is enough for most people in most
    Robin> time, but I am really hesitated to tell my friend once and
    Robin> once again "Sorry, but your name (羽中) is not supported by
    Robin> my emacs."

No, that's not my name.  I  think Gnus sets the charset of my postings
to big5.

And  which Emacs  is  your emacs?   Emacs  since version  20 has  been
displaying  Chinese  (I can't  speak  for  Japanese  and Korean)  very
satisfactorily.  And  I find  it, together with  Gnus, to be  the most
practical tool on Linux to read/write Chinese files/news/mails.



-- 
Lee Sau Dan                     李守敦(Big5)                    ~{@nJX6X~}(HZ) 

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

  reply	other threads:[~2003-05-15  8:07 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5730.1052348993.21513.help-gnu-emacs@gnu.org>
2003-05-10 14:26 ` Chinese characters support Kai Großjohann
2003-05-10 16:17   ` Charles Muller
2003-05-10 16:45     ` Kai Großjohann
2003-05-10 17:31       ` Charles Muller
2003-05-10 18:43         ` Eli Zaretskii
2003-05-11  2:11           ` Charles Muller
2003-05-11  3:32             ` Eli Zaretskii
2003-05-11 13:59               ` Charles Muller
     [not found]               ` <mailman.5976.1052661651.21513.help-gnu-emacs@gnu.org>
2003-05-12 19:29                 ` Jason Rumney
2003-05-12 19:58                 ` Kai Großjohann
2003-05-13  7:40                 ` Lee Sau Dan
2003-05-13  9:57                   ` acmuller
2003-05-13 10:02                   ` Robin Hu
2003-05-15  8:07                     ` Lee Sau Dan [this message]
2003-05-10 19:24         ` Kai Großjohann
2003-05-11  2:15           ` Charles Muller
2003-05-11  3:34             ` Eli Zaretskii
     [not found]           ` <mailman.5956.1052619415.21513.help-gnu-emacs@gnu.org>
2003-05-12 19:56             ` Kai Großjohann
2003-05-13  3:36               ` Charles Muller
2003-05-14  3:14                 ` Eli Zaretskii
     [not found]               ` <mailman.6084.1052797097.21513.help-gnu-emacs@gnu.org>
2003-05-13  7:05                 ` Kai Großjohann
2003-05-14  6:14                 ` Lee Sau Dan
2003-05-14 16:27                   ` Kai Großjohann
2003-05-14 21:07                     ` Jason Rumney
     [not found]       ` <mailman.5927.1052587973.21513.help-gnu-emacs@gnu.org>
2003-05-12 19:27         ` Jason Rumney
2003-05-13  7:40         ` Lee Sau Dan
2003-05-13 10:11           ` acmuller
2003-05-13 10:54           ` Charles Muller
     [not found]           ` <mailman.6097.1052826249.21513.help-gnu-emacs@gnu.org>
2003-05-15  8:07             ` Lee Sau Dan
2003-05-10 17:58     ` Eli Zaretskii
     [not found]     ` <mailman.5936.1052589798.21513.help-gnu-emacs@gnu.org>
2003-05-13  7:40       ` Lee Sau Dan
2003-05-14  3:15         ` Eli Zaretskii
     [not found]         ` <mailman.6156.1052882447.21513.help-gnu-emacs@gnu.org>
2003-05-15  8:07           ` Lee Sau Dan
2003-05-16 11:36             ` Eli Zaretskii
2003-05-12 23:05   ` Michael Na Li
2003-05-13  7:02     ` Kai Großjohann
     [not found]   ` <mailman.5922.1052583563.21513.help-gnu-emacs@gnu.org>
2003-05-13  7:40     ` Lee Sau Dan
2003-05-07 23:08 Gaoyan Xie
2003-05-08  6:27 ` Charles Muller
     [not found] ` <mailman.5739.1052375326.21513.help-gnu-emacs@gnu.org>
2003-05-08  7:33   ` Robin Hu
2003-05-10 14:28   ` Kai Großjohann

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=m3el31p71h.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).