From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: Re: Display of undisplayable characters: \U01F3A8 instead of diamond Date: Fri, 26 Aug 2022 10:37:32 +0200 Message-ID: <87a67rh037.fsf@dataswamp.org> References: <87bks77azu.fsf@gmail.com> <83zgfr1nnh.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40155"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:3zJWG2z0ER7lKn9Hku0135U3Q6o= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 26 10:38:50 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 1oRUrY-000ABq-TS for ged-emacs-devel@m.gmane-mx.org; Fri, 26 Aug 2022 10:38:48 +0200 Original-Received: from localhost ([::1]:35438 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oRUrX-0002fJ-UD for ged-emacs-devel@m.gmane-mx.org; Fri, 26 Aug 2022 04:38:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58492) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRUqW-0001ly-TJ for emacs-devel@gnu.org; Fri, 26 Aug 2022 04:37:44 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:40798) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRUqV-0002UD-7s for emacs-devel@gnu.org; Fri, 26 Aug 2022 04:37:44 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1oRUqS-0008UD-4p for emacs-devel@gnu.org; Fri, 26 Aug 2022 10:37:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action 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:294137 Archived-At: Eli Zaretskii wrote: > The diamond is a non-ASCII character, so to display it by default, > we'd need to make sure the terminal is capable of displaying it. You can print it in a Linux VT with printf -v tmp %04x 128 printf "\u${tmp}\n" > Also, do you really mean diamond, or do you mean U+FFFD > REPLACEMENT CHARACTER M-x insert-char RET fffd RET Indeed, looks like a diamond to me ... > And why the diamond, of all the possible characters? why not > simply '?', for example? Because then we would have to change the QUESTION MARK M-x insert-char RET 3f RET for the diamond instead ... > (FWIW, providing such an option makes very little sense to > me, for the reasons I explained in my previous message. > But if people insist, and if we can find a good and safe > replacement character to show instead of the hex code, > I won't object adding such an option.) Why isn't U+FFFD (�) safe? -- underground experts united https://dataswamp.org/~incal