From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: Emacs 22.1.90 can't save chinese-gb2312 file Date: Fri, 01 Feb 2008 14:00:34 +0900 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=ISO-2022-JP X-Trace: ger.gmane.org 1201842070 3860 80.91.229.12 (1 Feb 2008 05:01:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 1 Feb 2008 05:01:10 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, jasonr@gnu.org, emacs-devel@gnu.org To: "Zhang Wei" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 01 06:01:31 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JKo1q-0002cU-Cj for ged-emacs-devel@m.gmane.org; Fri, 01 Feb 2008 06:01:30 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKo1O-00028V-OY for ged-emacs-devel@m.gmane.org; Fri, 01 Feb 2008 00:01:02 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JKo1L-00028O-Pm for emacs-devel@gnu.org; Fri, 01 Feb 2008 00:00:59 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JKo1K-00026g-AC for emacs-devel@gnu.org; Fri, 01 Feb 2008 00:00:59 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKo1K-00026a-3W for emacs-devel@gnu.org; Fri, 01 Feb 2008 00:00:58 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JKo1J-0002MP-N0 for emacs-devel@gnu.org; Fri, 01 Feb 2008 00:00:57 -0500 Original-Received: from mail.gnu.org ([199.232.76.166] helo=mx10.gnu.org) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JKo1J-0004z5-Ea for emacs-pretest-bug@gnu.org; Fri, 01 Feb 2008 00:00:57 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JKo1G-0002Lz-Bs for emacs-pretest-bug@gnu.org; Fri, 01 Feb 2008 00:00:57 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JKo1F-0002Lb-GN; Fri, 01 Feb 2008 00:00:54 -0500 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id m1150Z4h028171; Fri, 1 Feb 2008 14:00:35 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp1.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id m1150YRc004130; Fri, 1 Feb 2008 14:00:34 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp1.aist.go.jp with ESMTP id m1150YUA010710; Fri, 1 Feb 2008 14:00:34 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.68) (envelope-from ) id 1JKo0w-0006d7-1i; Fri, 01 Feb 2008 14:00:34 +0900 In-reply-to: (id.brep@gmail.com) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-kernel: by monty-python.gnu.org: Solaris 8 (1) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:87907 gmane.emacs.pretest.bugs:20828 Archived-At: In article , "Zhang Wei" writes: > On 2/1/08, Zhang Wei wrote: > > When I save a file in gb2312 coding system, I got the following > > compliant, all of the chinese punctuation characters can't be encoded > > with gb2312: > > ------------------------------------------------------------------------------ > > These default coding systems were tried to encode text > > in the buffer `test': > > chinese-iso-8bit > > However, each of them encountered characters it couldn't encode: > > chinese-iso-8bit cannot encode these: ， 。 、 ？ > > > > Click on a character (or switch to this window by `C-x o' > > and select the characters by RET) to jump to the place it appears, > > where `C-u C-x =' will give information about it. > > > > Select one of the safe coding systems listed below, > > or cancel the writing with C-g and edit the buffer > > to remove or modify the problematic characters, > > or specify any other coding system (and risk losing > > the problematic characters). > > > > utf-8 utf-16 utf-16 utf-16 utf-16be utf-16le iso-2022-7bit > > -------------------------------------------------------------------------- > > C-u C-x = gives: > > -------------------------------------------------------------------------- > > character: 。 (302786, #o1117302, #x49ec2, U+3002) > > charset: mule-unicode-2500-33ff (Unicode characters of the range > > U+2500..U+33FF.) > > code point: #x3D #x42 > > syntax: w which means: word > > buffer code: #x9C #xF2 #xBD #xC2 > > file code: not encodable by coding system chinese-iso-8bit > > display: by this font (glyph code) > > -outline-Courier > > New-normal-r-normal-normal-13-97-96-96-c-*-iso10646-1 (#x3002) > > > > [back] > > -------------------------------------------------------------------------- > > > 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. --- Kenichi Handa handa@ni.aist.go.jp