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: raw-byte and char-table Date: Tue, 24 Aug 2010 20:08:33 +0300 Message-ID: <8362z0ndke.fsf@gnu.org> References: <83eidoogkc.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1282669609 3916 80.91.229.12 (24 Aug 2010 17:06:49 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 24 Aug 2010 17:06:49 +0000 (UTC) Cc: emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 24 19:06:48 2010 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.69) (envelope-from ) id 1OnwxR-00084a-5i for ged-emacs-devel@m.gmane.org; Tue, 24 Aug 2010 19:06:45 +0200 Original-Received: from localhost ([127.0.0.1]:47372 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OnwxQ-0003bu-Fd for ged-emacs-devel@m.gmane.org; Tue, 24 Aug 2010 13:06:44 -0400 Original-Received: from [140.186.70.92] (port=47183 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OnwxL-0003bi-EC for emacs-devel@gnu.org; Tue, 24 Aug 2010 13:06:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OnwxG-0007sP-G2 for emacs-devel@gnu.org; Tue, 24 Aug 2010 13:06:39 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:57833) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OnwxG-0007sD-8A for emacs-devel@gnu.org; Tue, 24 Aug 2010 13:06:34 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0L7O000002635400@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Tue, 24 Aug 2010 20:06:28 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.70.215.111]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L7O000C026R0J30@a-mtaout22.012.net.il>; Tue, 24 Aug 2010 20:06:28 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) 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:129162 Archived-At: > From: Kenichi Handa > Cc: emacs-devel@gnu.org > Date: Tue, 24 Aug 2010 13:29:45 +0900 > > In article <83eidoogkc.fsf@gnu.org>, Eli Zaretskii writes: > > > > A char-table is a table indexed by a character code. So, > > > it's 0xA0th element is a value for a character U+00A0. > > > Then, how to set/get a value for raw-byte 0xA0? Currently, > > > this is the way to do that: > > > > > > (aref CHAR-TABLE (unibyte-char-to-multibyte #xA0)) > > > (aset CHAR-TABLE (unibyte-char-to-multibyte #xA0) VALUE) > > > One could also use the codepoint of the corresponding eight-bit > > character directly, no? > > Like #x3FFFA0? It's possible but should not be recommended. Why not recommended? We already document in the ELisp manual the codepoints to which we map eight-bit bytes. It's not a secret, it's in the open. > As for a display table, we have one more problem. Currently > an element of a display table is nil or a vector of > characters. To directly output the byte #xA0 to a terminal, > perhaps the correct way is to set (unibyte-char-to-multibyte > #xA0) in a vector. That way, we can specify any byte(s) to > send to a terminal. > > But, then, what is the semantics of the vector element > (unibyte-char-to-multibyte #xA0) for a graphic device? What > should we display for CHAR if we setup > standard-display-table as this? > > (aset standard-display-table > CHAR (vector (unibyte-char-to-multibyte #xA0))) There's something I'm missing here: why text terminals and graphics terminals are different in this context? It seems that you are saying that was is correct for a text terminal does not have a clear semantics for a GUI terminal, but why?