From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: can not decode 0x93 and 0x94 to correct char Date: Fri, 28 Sep 2007 16:45:29 +0200 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: sea.gmane.org 1190990780 23622 80.91.229.12 (28 Sep 2007 14:46:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 28 Sep 2007 14:46:20 +0000 (UTC) Cc: william.xue@gmail.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 28 16:46:16 2007 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 1IbH6M-0005Ey-46 for ged-emacs-devel@m.gmane.org; Fri, 28 Sep 2007 16:45:58 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IbH6I-0001Iy-Oj for ged-emacs-devel@m.gmane.org; Fri, 28 Sep 2007 10:45:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IbH5y-0001CQ-Ed for emacs-devel@gnu.org; Fri, 28 Sep 2007 10:45:34 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IbH5w-0001Bi-Mk for emacs-devel@gnu.org; Fri, 28 Sep 2007 10:45:33 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IbH5w-0001Bf-J0 for emacs-devel@gnu.org; Fri, 28 Sep 2007 10:45:32 -0400 Original-Received: from nitzan.inter.net.il ([213.8.233.22]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IbH5w-0002x9-47 for emacs-devel@gnu.org; Fri, 28 Sep 2007 10:45:32 -0400 Original-Received: from HOME-C4E4A596F7 (IGLD-84-228-47-73.inter.net.il [84.228.47.73]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id HXH98579 (AUTH halo1); Fri, 28 Sep 2007 16:42:49 +0200 (IST) In-reply-to: (message from Stefan Monnier on Fri, 28 Sep 2007 09:50:47 -0400) X-Detected-Kernel: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (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:79996 Archived-At: > From: Stefan Monnier > Date: Fri, 28 Sep 2007 09:50:47 -0400 > Cc: emacs-devel@gnu.org > > > 1. emacs -q > > 2. open char_err_clip.c > > 3. \223GPL License\224 > > > please check screen shots for detail. > > The problem here seems to be the default coding system used by Emacs. > Apparently it uses something like latin-1 rather than something > like cp1252. Yes. However, I don't think this is a problem, see below. > I don't know enough about how such things are specified in > general (outside of Emacs) under w32 to be able to help any further, but all > I know is that maybe Emacs should try and figure out that your default coding > system should be cp1252. Maybe the problem is that Emacs doesn't try to do > it, or maybe ti doesn't know how to do it, or maybe it does it wrong, or > maybe it doesn't want to do it (e.g. because cp1252 covers the whole 256 > possible bytes so the auto-detection can't work well). Emacs on Windows looks up the UI language of the current user, and then sets up the language environment for that language. Most language environments do not specify cpNNNN as their preferred encodings, so neither does Emacs.