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: Fwd: Re: Inadequate documentation of silly characters on screen. Date: Thu, 19 Nov 2009 21:52:20 +0200 Message-ID: <834ooqqoln.fsf@gnu.org> References: <20091118191258.GA2676@muc.de> <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> 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 1258660360 15227 80.91.229.12 (19 Nov 2009 19:52:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Nov 2009 19:52:40 +0000 (UTC) Cc: dak@gnu.org, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 19 20:52:32 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 1NBD3P-0001Ya-Ik for ged-emacs-devel@m.gmane.org; Thu, 19 Nov 2009 20:52:31 +0100 Original-Received: from localhost ([127.0.0.1]:44020 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBD3O-0001m0-WE for ged-emacs-devel@m.gmane.org; Thu, 19 Nov 2009 14:52:31 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBD3I-0001lM-PH for emacs-devel@gnu.org; Thu, 19 Nov 2009 14:52:24 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBD3E-0001jp-7M for emacs-devel@gnu.org; Thu, 19 Nov 2009 14:52:24 -0500 Original-Received: from [199.232.76.173] (port=58016 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBD3E-0001jm-3m for emacs-devel@gnu.org; Thu, 19 Nov 2009 14:52:20 -0500 Original-Received: from mtaout21.012.net.il ([80.179.55.169]:48414) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NBD3B-0005Is-Tl; Thu, 19 Nov 2009 14:52:18 -0500 Original-Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0KTD00900GGY9100@a-mtaout21.012.net.il>; Thu, 19 Nov 2009 21:52:13 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.70.37.193]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KTD0099MGJ02I10@a-mtaout21.012.net.il>; Thu, 19 Nov 2009 21:52:13 +0200 (IST) In-reply-to: <20091119180848.GE1314@muc.de> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.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:117290 Archived-At: > Date: Thu, 19 Nov 2009 18:08:48 +0000 > From: Alan Mackenzie > Cc: emacs-devel@gnu.org >=20 > No, you (all of you) are missing the point. That point is that if = an > Emacs Lisp hacker writes "?=F1", it should work, regardless of > what "codepoint" it has, what "bytes" represent it, whether those > "bytes" are coded with a different codepoint, or what have you. No can do, as long as we support both unibyte and multibyte buffers and strings. > OK. Surely displaying it as "\361" is a bug? It's no more a bug than this: M-: ?a RET =3D> 97 If `a' can be represented as 97, then why cannot \361 be represented as 4194289? > So, how did the character "=F1" get turned into the illegal byte #x= f1? It did so because you used aset to put it into a unibyte string. > Are you saying that Emacs is converting "?=F1" and "?=E4" into the = wrong > integers? Emacs can convert it into 2 distinct integer representations. It decides which one by the context. And you just happened to give it the wrong context. > What is the correct Emacs internal representation for "=F1" and "= =E4"? That depends on whether they will be put into a multibyte string/buffer or a unibyte one. > > Because Emacs has no separate "character" data type. >=20 > For which I am thankful. Then please understand that there's no bug here.