all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Kenichi Handa <handa@ni.aist.go.jp>
Cc: emacs-pretest-bug@gnu.org, Zhang Wei <id.brep@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Emacs 22.1.90 can't save chinese-gb2312 file
Date: Fri, 01 Feb 2008 08:46:31 +0000	[thread overview]
Message-ID: <47A2DC67.7070804@gnu.org> (raw)
In-Reply-To: <E1JKo0w-0006d7-1i@etlken.m17n.org>

Kenichi Handa wrote:
> In article <ebaf065f0801312030x70d3fb7aj96368c58cb8763c7@mail.gmail.com>, "Zhang Wei" <id.brep@gmail.com> writes:
>
>   
>> This bug crept in due to the changes of w32term.c since 2007-12-12, I
>> think, when I revert the changes of this file, the bug is gone.
>>     
>
> Are you sure?  It's quite surprising that the code in
> w32term.c affects encoding of characters.
>   


The change affects how keyboard input is handled. Before the change,
input was sent in gb2312 encoding one byte at a time, and encoded-kbd
was used to decode the input. After the change, input is sent in
mule-unicode-* charsets where possible.

So the punctuation has changed in representation from gb2312 to
mule-unicode-2500-33ff, while Hanzi is outside the range covered by the
mule-unicode charsets, so continues to be sent as gb2312.

Emacs knows how to do the conversion, as writing the file as utf-8 then
reading and writing out as gb2312 is reported to work, it just doesn't
do the conversion in this case.





      parent reply	other threads:[~2008-02-01  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 16:05 Emacs 22.1.90 can't save chinese-gb2312 file Zhang Wei
2008-02-01  4:30 ` Zhang Wei
2008-02-01  5:00   ` Kenichi Handa
2008-02-01  6:55     ` Zhang Wei
2008-02-01  7:09     ` Zhang Wei
2008-02-01  8:14       ` Kenichi Handa
2008-02-01  8:38         ` Zhang Wei
2008-02-01  8:46     ` Jason Rumney [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47A2DC67.7070804@gnu.org \
    --to=jasonr@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=handa@ni.aist.go.jp \
    --cc=id.brep@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.