unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Shaddy Baddah <Shaddy.Baddah@msa.hinet.net>
Subject: More unicode blocks?
Date: Sun, 25 Sep 2005 02:28:00 +0800	[thread overview]
Message-ID: <43359AB0.1050300@msa.hinet.net> (raw)

Hi,

Today, I finally did what I had resolved to do some time ago. I delved
into emacs's unicode support facilities.

I am a little disappointed, because it has become apparent that the
unicode character set support is limited to 3 specific blocks of the
full unicode character set, those being the blocks that start and end at
the indexes expressed in mule-unicode-0100-24ff, mule-unicode-2500-33ff
and mule-unicode-e000-ffff.

The blocks that I am interested in are the CJK Unified Ideographs blocks
, that start at unicode index 0x4E00. Specifically, the characters that
are shared by the character set encoded via the big5 encoding scheme.

I have no problems displaying and editing these characters under the
big5 coding scheme, so they are obviously well supported by emacs (and
it's internal coding scheme, right?).

So, what is the impediment, or perhaps rationale, behind the lack of
support for the additional unicode blocks at this stage of Emacs
development?

Is it simply to do with someone having to implement some type of
character translation tables, or is there/how much more is there to it?

Regards,
Shaddy

P.S: please honour my reply-to email field.

             reply	other threads:[~2005-09-24 18:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24 18:28 Shaddy Baddah [this message]
2005-09-28 14:59 ` More unicode blocks? Shaddy Baddah
     [not found] ` <mailman.8992.1127919972.20277.help-gnu-emacs@gnu.org>
2005-09-28 15:31   ` Charles philip Chan
2005-09-28 15:53   ` Thien-Thi Nguyen
2005-09-28 18:22 ` Kevin Rodgers

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=43359AB0.1050300@msa.hinet.net \
    --to=shaddy.baddah@msa.hinet.net \
    --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).