From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Aidan Kehoe Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: [PATCH] Unicode Lisp reader escapes. Date: Sun, 18 Jun 2006 18:11:06 +0200 Message-ID: <17557.31514.794081.590563@parhasard.net> References: <17491.34779.959316.484740@parhasard.net> <17492.29148.246942.842300@parhasard.net> <8764kkawsf.fsf@jurta.org> <87vesi6nh1.fsf@jurta.org> <878xp8g2a9.fsf@jurta.org> <17537.54719.354843.89030@parhasard.net> <17553.43278.718379.863167@parhasard.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1150646906 6882 80.91.229.2 (18 Jun 2006 16:08:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 18 Jun 2006 16:08:26 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 18 18:08:25 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Frzoy-00031R-Uj for ged-emacs-devel@m.gmane.org; Sun, 18 Jun 2006 18:08:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Frzoy-0005GL-FI for ged-emacs-devel@m.gmane.org; Sun, 18 Jun 2006 12:08:20 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Frzok-0005Bz-Ds for emacs-devel@gnu.org; Sun, 18 Jun 2006 12:08:06 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Frzoj-0005A0-Ca for emacs-devel@gnu.org; Sun, 18 Jun 2006 12:08:05 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Frzoj-00059i-7b; Sun, 18 Jun 2006 12:08:05 -0400 Original-Received: from [66.111.49.30] (helo=icarus.asclepian.ie) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Frzyj-0006bm-AW; Sun, 18 Jun 2006 12:18:25 -0400 Original-Received: by icarus.asclepian.ie (Postfix, from userid 1003) id 8F9EF8008C; Sun, 18 Jun 2006 17:07:52 +0100 (IST) Original-To: Eli Zaretskii In-Reply-To: X-Mailer: VM 7.17 under 21.5 (beta26) "endive" (+CVS-20060512) XEmacs Lucid X-NS5-file-as-sent: t X-Echelon-distraction: $400 million in gold bullion quiche SCUD missile Croatian Mossad constitution 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:55983 gmane.emacs.pretest.bugs:12545 Archived-At: Ar an seacht=C3=BA l=C3=A1 d=C3=A9ag de m=C3=AD Meitheamh, scr=C3=ADobh = Eli Zaretskii:=20 > > > Is it to trigger an "Invalid character" message, or is something = else > > > going on here? > >=20 > > It doesn't actually trigger a message, it displays a character to be > > interpreted as ``the character couldn't be interpreted.'' >=20 > But in my testing, I do see an "Invalid character" message. Yes. That=E2=80=99s because I yanked the wrong charset from charset.h whe= n porting the code from XEmacs, and the attempt to create two-dimensional character= in JISX0201 fails, as it should, since JISX0201 is a one-dimensional charact= er set.=20 The code as intended, doesn=E2=80=99t trigger the message. As it was writ= ten, to my discredit, it did. > Could you please show an example of using this new function to produce > this special ``character that couldn't be interpreted''? > > My feeling is that the syntax should be close in its behaviour to wh= at the > > coding systems do, and when the coding systems see a code point that= is > > valid but that they can't interpret, they trash the user's data. >=20 > This function is not about coding systems, it's about character sets. This function is about transformation from an external format to the editor=E2=80=99s internal format. Which is a big part of what coding syst= ems do. So some parallels in our approach is reasonable. > Coding systems already replace unsupported characters with `?' (other > applications behave like that as well), so perhaps we should use some > more conventional character here. > Does anyone have an opinion? Perhaps, indeed. --=20 Aidan Kehoe, http://www.parhasard.net/