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: Display of characters #xa0 and #xad in unibyte buffers Date: Mon, 28 Sep 2009 08:43:09 +0200 Message-ID: <831vlrsh6q.fsf@gnu.org> References: <19131.35568.835627.216245@a1i15.kph.uni-mainz.de> <833a6bv30o.fsf@gnu.org> <19132.34451.565451.857731@a1ihome1.kph.uni-mainz.de> <83ws3ntmgv.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1254120083 6846 80.91.229.12 (28 Sep 2009 06:41:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Sep 2009 06:41:23 +0000 (UTC) Cc: ulm@gentoo.org, emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 28 08:41:16 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 1Ms9v9-0006sA-2v for ged-emacs-devel@m.gmane.org; Mon, 28 Sep 2009 08:41:15 +0200 Original-Received: from localhost ([127.0.0.1]:43967 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ms9v8-0004cq-98 for ged-emacs-devel@m.gmane.org; Mon, 28 Sep 2009 02:41:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ms9v2-0004cl-TZ for emacs-devel@gnu.org; Mon, 28 Sep 2009 02:41:08 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ms9v1-0004cZ-Pt for emacs-devel@gnu.org; Mon, 28 Sep 2009 02:41:08 -0400 Original-Received: from [199.232.76.173] (port=45900 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ms9v1-0004cW-KK for emacs-devel@gnu.org; Mon, 28 Sep 2009 02:41:07 -0400 Original-Received: from mtaout6.012.net.il ([84.95.2.16]:37765) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ms9v1-0006A0-5i for emacs-devel@gnu.org; Mon, 28 Sep 2009 02:41:07 -0400 Original-Received: from conversion-daemon.i-mtaout6.012.net.il by i-mtaout6.012.net.il (HyperSendmail v2007.08) id <0KQO003004ZTQM00@i-mtaout6.012.net.il> for emacs-devel@gnu.org; Mon, 28 Sep 2009 08:41:05 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([77.126.56.156]) by i-mtaout6.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KQO00F3Y58GDA50@i-mtaout6.012.net.il>; Mon, 28 Sep 2009 08:41:05 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (1203?) 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:115711 Archived-At: > From: Kenichi Handa > Cc: ulm@gentoo.org, emacs-devel@gnu.org > Date: Mon, 28 Sep 2009 10:10:32 +0900 >=20 > In article <83ws3ntmgv.fsf@gnu.org>, Eli Zaretskii w= rites: >=20 > > > >> $ emacs -Q > > > >> M-x toggle-enable-multibyte-characters RET C-q 240 RET C-q 2= 55 RET > > > >>=20 > > > >> The characters are displayed as "_-" (approximately). > > > >>=20 > > > >> Shouldn't they be displayed as "\240\255", considering that = these are > > > >> raw bytes with no specific meaning? > > >=20 > > > > There are no ``raw bytes'' in a unibyte buffer. Every byte t= here is > > > > interpreted as a character, and shown as such. This is the m= ain > > > > feature of unibyte buffers; otherwise, who'd want them? >=20 > I think the main feature of unibyte buffers is to handle > raw-bytes as is. How do we even know that they are raw bytes, and how do we distinguish, in a unibyte buffer, =FC from \374, say? Just because t= hey were inserted by C-q NNN or by some other mechanism? > For those who want to see a raw-byte as a character of their locale > (language environment), we have > unibyte-display-via-language-environment. I thought bytes in unibyte buffers are always interpreted as characters of the locale, as Emacs 19 did. Are you saying that they are by default always interpreted as raw bytes, unless unibyte-display-via-language-environment is set?