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: 22.2.50; Display of "zero width no-break space" (U+FEFF) Date: Mon, 21 Apr 2008 06:09:33 +0300 Message-ID: References: <87fxtgt7fo.fsf@jurta.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 1208747407 3623 80.91.229.12 (21 Apr 2008 03:10:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Apr 2008 03:10:07 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 21 05:10:42 2008 connect(): Connection refused 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 1JnmQS-0001UP-EE for ged-emacs-devel@m.gmane.org; Mon, 21 Apr 2008 05:10:40 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JnmPn-0004GC-AB for ged-emacs-devel@m.gmane.org; Sun, 20 Apr 2008 23:09:59 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JnmPj-0004Dm-2b for emacs-devel@gnu.org; Sun, 20 Apr 2008 23:09:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JnmPh-0004CF-H2 for emacs-devel@gnu.org; Sun, 20 Apr 2008 23:09:54 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JnmPh-0004CC-9R for emacs-devel@gnu.org; Sun, 20 Apr 2008 23:09:53 -0400 Original-Received: from mtaout1.012.net.il ([84.95.2.1]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JnmPg-0001qd-H0 for emacs-devel@gnu.org; Sun, 20 Apr 2008 23:09:52 -0400 Original-Received: from HOME-C4E4A596F7 ([80.230.59.104]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0JZN00LDYO3HG570@i-mtaout1.012.net.il> for emacs-devel@gnu.org; Mon, 21 Apr 2008 06:23:41 +0300 (IDT) In-reply-to: <87fxtgt7fo.fsf@jurta.org> X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 9.1 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:95592 Archived-At: > From: Juri Linkov > Date: Mon, 21 Apr 2008 02:57:29 +0300 > Cc:=20 >=20 > >> in Emacs 22.2.50, "zero width no-break space" (U+FEFF) is displa= yed as > >> a hollow box. [1] > >> > >> I think for normal buffers it should be displayed like `=A0' (NO= -BREAK > >> SPACE, U+00A0) i.e. using the face face `nobreak-space'. But wh= en > >> `nobreak-char-display' is nil, it should not be displayed at all= or > >> like a normal SPC. (Dunno what Unicode says about it.) > > > > Any opinions on this? >=20 > This is the same character as BOM. But since it is *ZERO-WIDTH* > NO-BREAK SPACE, it seems it shouldn't be displayed at all in view m= ode. > But it edit mode, it would be preferable to have some indication > about the presence of this character in the buffer. I think there will be many characters such as U+FEFF defined by Unicode that we will need to decide how to display in various modes. It's not right, IMO, to decide about their display one by one, when someone happens to pop a question. We should probably have some kind of general policy about them. I suggest that Someone(TM) looks at this issue and suggests how we should deal with these characters, based on Unicode recommendations and on what other Unicode-capable editors do.