From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Display of undisplayable characters: \U01F3A8 instead of diamond Date: Tue, 30 Aug 2022 15:15:09 +0300 Message-ID: <83bks2udv6.fsf@gnu.org> References: <87edx28cl1.fsf@disroot.org> <83y1v7w6eu.fsf@gnu.org> <83pmgiufeq.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36256"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 30 14:18:09 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oT0C0-0009Gf-37 for ged-emacs-devel@m.gmane-mx.org; Tue, 30 Aug 2022 14:18:08 +0200 Original-Received: from localhost ([::1]:47368 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oT0Bz-0000aY-5l for ged-emacs-devel@m.gmane-mx.org; Tue, 30 Aug 2022 08:18:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54512) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oT08n-0005wl-Bx for emacs-devel@gnu.org; Tue, 30 Aug 2022 08:14:50 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:40404) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oT08n-0007hN-2z for emacs-devel@gnu.org; Tue, 30 Aug 2022 08:14:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=+A+xkJkz+9/bWFTnyFMhhvMWDEOL2OceCAn+SdlPqDY=; b=TZRlonOluBfa dQPMdJec8/XAOheFIMMBr2Ow4TBw+vTT9/cbCQbX57ESTu9b4eWyO3FU3NFLwNkEO07ipXb2boh0x FpsxuvZyhlFCdqgIG15o0BogMjBrdZLeTvPjSh137RLCzXhNiQ1sI8tj6E9XKjhDp+2uBSqSgVZ3B 0f8S0fYnL0oQbuk0LXMPUwPsmHhgXmqpeTRBPu3yss8uIknAUCiFktizmwWZUmdzQWgoUdqc1iyaQ gIUgMk/fqcBOgv8xUsMgYo9Aftm/j7gA5GogFzOoTYji4wZ8RMeAvHQvHkPIMfz3IkkbJCQn+Jidx rDkoigzpeFc7PjO6OHjEAg==; Original-Received: from [87.69.77.57] (port=4990 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oT08l-0007FF-CC; Tue, 30 Aug 2022 08:14:47 -0400 In-Reply-To: <83pmgiufeq.fsf@gnu.org> (message from Eli Zaretskii on Tue, 30 Aug 2022 14:41:49 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:294337 Archived-At: > Date: Tue, 30 Aug 2022 14:41:49 +0300 > From: Eli Zaretskii > Cc: emacs-devel@gnu.org > > > Using several disjoint ranges could do the job, I suppose, > > if someone can tell me how to determine what those ranges should be. > > > > Could this be figured out automatically by calling char-displayable-p > > on each character code? > > Such a code can be written, and can use char-displayable-p, indeed. > > > Up to what number would that loop have to run? > > Up to (and including) #x10FFFF. That's the theory, of course. In practice, with the Linux console, you could only run the loop till #xFFFF, I guess, and just assume the rest of the characters are not displayable without checking.