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: On the masking of undisplayable characters Date: Tue, 07 Jul 2015 05:43:26 +0300 Message-ID: <83vbdwvga9.fsf@gnu.org> References: <83wpydup68.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1436237036 15927 80.91.229.3 (7 Jul 2015 02:43:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 7 Jul 2015 02:43:56 +0000 (UTC) Cc: emacs-devel@gnu.org To: bruce.connor.am@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 07 04:43:48 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZCIrJ-0004bZ-Vi for ged-emacs-devel@m.gmane.org; Tue, 07 Jul 2015 04:43:46 +0200 Original-Received: from localhost ([::1]:53746 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZCIrI-0002fk-Ex for ged-emacs-devel@m.gmane.org; Mon, 06 Jul 2015 22:43:44 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZCIrF-0002ff-Dt for emacs-devel@gnu.org; Mon, 06 Jul 2015 22:43:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZCIrB-0005ZF-SQ for emacs-devel@gnu.org; Mon, 06 Jul 2015 22:43:41 -0400 Original-Received: from mtaout21.012.net.il ([80.179.55.169]:49255) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZCIrB-0005Z6-KW for emacs-devel@gnu.org; Mon, 06 Jul 2015 22:43:37 -0400 Original-Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0NR300F00IPL8C00@a-mtaout21.012.net.il> for emacs-devel@gnu.org; Tue, 07 Jul 2015 05:43:36 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NR300FOXJKN7850@a-mtaout21.012.net.il>; Tue, 07 Jul 2015 05:43:36 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:187756 Archived-At: > Date: Mon, 6 Jul 2015 20:57:08 +0100 > From: Artur Malabarba > Cc: emacs-devel > > > What characters are you talking about, specifically? > > Round quotes were displayed as hard quotes. The reason this happened on my pc > was a bug, but I understand that for systems that really can't display them > this is what will happen. > > I didn't check whether this applies to any other characters. I was just > surprised to find out the file was not being displayed as-is without so much as > a notice. It should happen only with quotes, and presumably only in documentation-related buffers. The rationale is that we cannot afford showing illegible documentation to users just because their terminal is incapable of displaying these important characters. I suggested to limit this to windows showing *Help* buffers, but it was decided to wait until someone complains. > > It's hard to respond without knowing the details. Most of the uses of > > display tables I know of are there for ages, so adding some kind of > > message about that now would seem inappropriate. (And when exactly do > > we display that message? when the character is first displayed?) > > When visiting the file and when the character is typed for the first time, > would be an option. Not really: the display engine doesn't examine any of those characters, until they are on or very near to the visible portion of the buffer. > > the glyphless-char-display feature, > > I don't know which characters are affected by this. Those that cannot be displayed by any fonts.