From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: 23.0.60; end-of-sentence and non-breaking space Date: Fri, 02 Jan 2009 22:06:21 -0500 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1230952004 1142 80.91.229.12 (3 Jan 2009 03:06:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 3 Jan 2009 03:06:44 +0000 (UTC) Cc: cyd@stupidchicken.com, 1726@emacsbugs.donarmstrong.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 03 04:07:54 2009 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 1LIwrg-0004gg-8b for ged-emacs-devel@m.gmane.org; Sat, 03 Jan 2009 04:07:52 +0100 Original-Received: from localhost ([127.0.0.1]:53435 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LIwqR-0007RH-89 for ged-emacs-devel@m.gmane.org; Fri, 02 Jan 2009 22:06:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LIwqJ-0007Qk-VW for emacs-devel@gnu.org; Fri, 02 Jan 2009 22:06:28 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LIwqI-0007QG-9r for emacs-devel@gnu.org; Fri, 02 Jan 2009 22:06:27 -0500 Original-Received: from [199.232.76.173] (port=39500 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LIwqI-0007QB-2j for emacs-devel@gnu.org; Fri, 02 Jan 2009 22:06:26 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:35139 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LIwqG-0004pY-9V; Fri, 02 Jan 2009 22:06:24 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArcEAF9lXklFxLKh/2dsb2JhbACBashShXKBaQ X-IronPort-AV: E=Sophos;i="4.36,320,1228107600"; d="scan'208";a="31741728" Original-Received: from 69-196-178-161.dsl.teksavvy.com (HELO ceviche.home) ([69.196.178.161]) by ironport2-out.teksavvy.com with ESMTP; 02 Jan 2009 22:06:21 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id 626D4B41B8; Fri, 2 Jan 2009 22:06:21 -0500 (EST) In-Reply-To: (Richard M. Stallman's message of "Fri, 02 Jan 2009 12:13:58 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:107540 Archived-At: > This raw-byte char is what used to be called an eight-bit-control (or > eight-bit-graphic depending on the actual value) char. > I.e. "\xa0" is treated as a string that contains the \xa0 byte (i.e. an > eight-bit-* (aka raw-byte) char) rather than the \xa0 char (a latin-1 > non-breaking space). > 1. Is that the right thing for \xa0 in a string to mean? > Or should it mean the character with code xa0? > 2. I find it hard to think about that question since I don't see any > documentation explaining how this ought to work. That documentation > is essential. Good point. Especially because I think this changed from Emacs-20 to Emacs-21, and I think it also changed now from Emacs-22 to Emacs-23. IIUC if you want the character with code #xa0, then using \u00a0 would seem like the most unambiguous option (I notice that "\ua0" gives a weird error "Non-hex digit used for Unicode escape"). Not sure what \NNN or \xMM should do. Stefan