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: Displaying bytes Date: Mon, 23 Nov 2009 20:28:54 -0500 Message-ID: References: <20091119082040.GA1720@muc.de> <874ooq8xay.fsf@wanchan.jasonrumney.net> <20091119141852.GC1720@muc.de> <20091119155848.GB1314@muc.de> <87aayiihe9.fsf@lola.goethe.zz> <20091119180848.GE1314@muc.de> <47325.130.55.118.19.1258658705.squirrel@webmail.lanl.gov> <20091119212550.GG1314@muc.de> <87my2ign8u.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: ger.gmane.org 1259026165 28792 80.91.229.12 (24 Nov 2009 01:29:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 24 Nov 2009 01:29:25 +0000 (UTC) Cc: dak@gnu.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 24 02:29:18 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 1NCkDW-0002rv-0f for ged-emacs-devel@m.gmane.org; Tue, 24 Nov 2009 02:29:18 +0100 Original-Received: from localhost ([127.0.0.1]:56759 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCkDV-0002m7-Iu for ged-emacs-devel@m.gmane.org; Mon, 23 Nov 2009 20:29:17 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCkDM-0002kJ-SY for emacs-devel@gnu.org; Mon, 23 Nov 2009 20:29:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCkDH-0002fm-9v for emacs-devel@gnu.org; Mon, 23 Nov 2009 20:29:07 -0500 Original-Received: from [199.232.76.173] (port=57255 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCkDH-0002fV-1o for emacs-devel@gnu.org; Mon, 23 Nov 2009 20:29:03 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:57285 helo=ironport2-out.pppoe.ca) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NCkDB-00015B-Uj; Mon, 23 Nov 2009 20:28:58 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnsFADLFCkvO+IIa/2dsb2JhbACBTtUuhDwEgXCIEg X-IronPort-AV: E=Sophos;i="4.47,275,1257138000"; d="scan'208";a="49893240" Original-Received: from 206-248-130-26.dsl.teksavvy.com (HELO pastel.home) ([206.248.130.26]) by ironport2-out.pppoe.ca with ESMTP; 23 Nov 2009 20:28:57 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id ED96180E5; Mon, 23 Nov 2009 20:28:56 -0500 (EST) In-Reply-To: (Richard Stallman's message of "Mon, 23 Nov 2009 15:38:41 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (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:117656 Archived-At: --=-=-= Content-Type: text/plain; charset=iso-8859-1 > For instance, C-u C-x = on \224 says > character: (4194196, #o17777624, #x3fff94) > preferred charset: tis620-2533 (TIS620.2533) > code point: 0x94 > syntax: w which means: word > buffer code: #x94 > file code: #x94 (encoded by coding system no-conversion) > display: not encodable for terminal Here C-u C-x = tells me: --=-=-= Content-Transfer-Encoding: 8bit character: ¡ (4194209, #o17777641, #x3fffa1) preferred charset: eight-bit (Raw bytes 128-255) code point: 0xA1 syntax: w which means: word buffer code: #xA1 file code: not encodable by coding system utf-8-unix display: no font available I don't know you see this "tis620" stuff. --=-=-= Content-Type: text/plain; charset=iso-8859-1 > Perhaps it should say, > character: Stray byte (4194196, #o17777624, #x3fff94) We could do that indeed. > What are the situations where a user is likely to see these stray > bytes. There pretty much shouldn't be any in multibyte buffers. > When visiting a binary file, of course; but in that situation, > nobody will be surprised or disappointed. And presumably for binary files, the buffer will be unibyte. > (It is also not clear to me what "ASCII compatible" means in this > context.) It means that the lower 128 chars coincide with those of ASCII. Stefan --=-=-=--