From: Jason Rumney <jasonr@gnu.org>
To: Kenichi Handa <handa@ni.aist.go.jp>
Cc: emacs-pretest-bug@gnu.org, yujie052@gmail.com
Subject: Re: Fwd: 23.0.50; can't input chinese punctuation on w32 platform
Date: Fri, 01 Feb 2008 14:07:35 +0000 [thread overview]
Message-ID: <47A327A7.4060806@gnu.org> (raw)
In-Reply-To: <E1JKqMQ-0000ZK-4Y@etlken.m17n.org>
Kenichi Handa wrote:
> In article <479B4BE3.2000204@gnu.org>, Jason Rumney <jasonr@gnu.org> writes:
>
>
>> This seems to be a problem with mule-unicode-2500-33ff to gb2312
>> encoding. I doubt it is limited to w32.
>>
>
> Right. This is because of the limitation of Emacs 22's
> Unicode handling. If you want to handle U+3002, you have
> to use UTF-* coding systems.
>
> It will be fixed by Emacs 23.
>
Meanwhile we need to handle keyboard input in Emacs 22.2 in a way that
is not any worse than 22.1.
AFAICT, CJK punctuation, Kana, Jamo, Kanbun, Bopomofo, CJK radicals,
Thai and possibly Greek and Cyrillic are potentially problematic. Am I
correct in thinking that Latin character sets are not affected?
Is there a well defined range of unicode that does or doesn't support
conversion? Doesn't pasting from the clipboard have the same problem?
next prev parent reply other threads:[~2008-02-01 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42b562540801260432h43921157k7d4034ddfff28862@mail.gmail.com>
2008-01-26 15:04 ` Fwd: 23.0.50; can't input chinese punctuation on w32 platform Jason Rumney
2008-02-01 7:30 ` Kenichi Handa
2008-02-01 12:33 ` yu jie
2008-02-01 14:07 ` Jason Rumney [this message]
2008-02-01 15:37 ` Eli Zaretskii
2008-02-01 16:05 ` Jason Rumney
2008-02-02 1:37 ` YAMAMOTO Mitsuharu
2008-02-02 10:22 ` Eli Zaretskii
[not found] ` <47A8FEBA.8000304@gnu.org>
2008-02-06 9:57 ` 23.0.50; can't input chinese punctuation on win32 platform Zhang Wei
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=47A327A7.4060806@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=handa@ni.aist.go.jp \
--cc=yujie052@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.