From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Zhang Wei" Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: Emacs 22.1.90 can't save chinese-gb2312 file Date: Fri, 1 Feb 2008 12:30:36 +0800 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1201840253 32486 80.91.229.12 (1 Feb 2008 04:30:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 1 Feb 2008 04:30:53 +0000 (UTC) To: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org, jasonr@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 01 05:31:14 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 1JKnYW-0005RE-LX for ged-emacs-devel@m.gmane.org; Fri, 01 Feb 2008 05:31:12 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKnY5-0008HS-3q for ged-emacs-devel@m.gmane.org; Thu, 31 Jan 2008 23:30:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JKnY0-0008Fs-M9 for emacs-devel@gnu.org; Thu, 31 Jan 2008 23:30:40 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JKnXz-0008ER-1j for emacs-devel@gnu.org; Thu, 31 Jan 2008 23:30:39 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKnXy-0008EJ-ID for emacs-devel@gnu.org; Thu, 31 Jan 2008 23:30:38 -0500 Original-Received: from wx-out-0506.google.com ([66.249.82.227]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JKnXy-0006Cv-6b for emacs-devel@gnu.org; Thu, 31 Jan 2008 23:30:38 -0500 Original-Received: by wx-out-0506.google.com with SMTP id s7so1010065wxc.24 for ; Thu, 31 Jan 2008 20:30:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=/yNZ/S8pTpp4kdp6Ec+fHCkQHl8DK2lJSF2gAL4w4/U=; b=VgDG55iM4RdXMQX7GHTFbIWPPKG5eaK4C9278wWhNcJhHQZu7jKnVqVUvgvKYY1ei8bD28Xp8zaiHruLqbW+zIFmQ5DjtzhkzrKVqHU/+F4PQ5QT7xGLN5bXO3V5z+IgA4SnvoNUajsIJ2xUlc8L5Zuk4jqVIk3gzJmcCOp+4ys= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DQ5svcMUmEeetlFP3tdom9tm2OyIzXrBsefJM2uwgZSAZjhenrC2wnhTPaW26zGvSnVRnjyUNVvUgwBKaMSHpgrqiKBQG2i3tljjEwWDNeC+m1un+Dlph+96mpNBrPm/40bDSMMBDSDJZP7aPSuv1QdJwSYMPOyz7Qgk69Icz4U= Original-Received: by 10.150.58.5 with SMTP id g5mr1102379yba.89.1201840236801; Thu, 31 Jan 2008 20:30:36 -0800 (PST) Original-Received: by 10.150.217.4 with HTTP; Thu, 31 Jan 2008 20:30:36 -0800 (PST) In-Reply-To: Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) 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:87905 gmane.emacs.pretest.bugs:20827 Archived-At: 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.