From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Kenichi Handa <handa@m17n.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: chinese-gbk
Date: Tue, 23 Oct 2007 10:59:01 +0900 [thread overview]
Message-ID: <b4modeqiobe.fsf@jpl.org> (raw)
In-Reply-To: <E1Ik8yF-0003tU-S6@etlken.m17n.org>
>>>>> Kenichi Handa wrote:
> In article <b4mzlyaogxg.fsf@jpl.org>, Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> Is it possible to implement the `chinese-gbk' coding system (and
>> also the charset) to the EMACS_22_BASE branch (i.e., Emacs 22.2)?
> The coding system is possible by mapping characters into
> various existing CJ characters if we can ignore rarely used
> few handreds characters. The code will be something like
> the support of utf-8.
> But, Emacs 22 does't have a room to to make a charset for
> GBK.
Oops. I wasn't aware of it. Thanks.
next prev parent reply other threads:[~2007-10-23 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 23:42 chinese-gbk Katsumi Yamaoka
2007-10-23 1:54 ` chinese-gbk Kenichi Handa
2007-10-23 1:59 ` Katsumi Yamaoka [this message]
2007-10-23 6:51 ` chinese-gbk Zhang Wei
2007-10-23 8:38 ` chinese-gbk Katsumi Yamaoka
2007-10-23 8:55 ` chinese-gbk Katsumi Yamaoka
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4modeqiobe.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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 NNTP newsgroup(s).