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: Sat, 27 Aug 2022 10:12:59 +0300 Message-ID: <835yie17no.fsf@gnu.org> References: <87y1vaobq8.fsf@dataswamp.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40322"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Emanuel Berg Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 27 09:13:49 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 1oRq0r-000AKb-IS for ged-emacs-devel@m.gmane-mx.org; Sat, 27 Aug 2022 09:13:49 +0200 Original-Received: from localhost ([::1]:47946 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oRq0q-0000Mp-22 for ged-emacs-devel@m.gmane-mx.org; Sat, 27 Aug 2022 03:13:48 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33148) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRpzq-000819-4h for emacs-devel@gnu.org; Sat, 27 Aug 2022 03:12:46 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33368) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRpzp-0007ZX-Dm; Sat, 27 Aug 2022 03:12:45 -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=rIcy+C8YrCXR94WHx8fHj/29vIbphO5CFeM/YQOqmQ4=; b=QHaIMejBDxpj PgFXSWGcts4SCm7+sT9jTxKWaxYiI35GUTN18S7x78AVVRierVIbS6L3En/4+GlEGjQfWBjSDWsw8 q1LZMpaxtebbWkRsuMDTow5TacaEtONDykfUByDK0fy1hNAAjf4VQtl+/+CZkgpVbLWzFYvd+gYDe psnvdZIFCRs/erTO2yO5/9O/s/6SuJiJ84/EDCVk0tYAwhYRM9fwVJPkRELW0jm2xcU58pyC+4fmy DrJaGsjjH4KFIFPs1yGGa7cgOaNTRlGATDvnm+Ry+sP9CGWJYpW+dkCVZPK5EWswixpdaC90aXXTb 4GdHOiKPpynf++/iKecJrQ==; Original-Received: from [87.69.77.57] (port=2921 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 1oRpzo-0007y2-LT; Sat, 27 Aug 2022 03:12:44 -0400 In-Reply-To: <87y1vaobq8.fsf@dataswamp.org> (message from Emanuel Berg on Sat, 27 Aug 2022 00:56:31 +0200) 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:294177 Archived-At: > From: Emanuel Berg > Date: Sat, 27 Aug 2022 00:56:31 +0200 > > And in particular because we had the old style already so we > should know how to do that already No, we didn't "have the old style". We had a bug: we sent to a terminal a character code that it cannot display. That should never happen in Emacs. That bug is now fixed, and such characters are considered as not displayable by the terminal, as they should be. We are not going back to the situation where we sent to the Linux console character codes for which it couldn't produce valid glyphs. People who suggest sending U+FFFD to the Linux console should first verify whether the console is capable of displaying that character. One way of verifying this is to type C-x 8 RET fffd RET in an Emacs session which displays on the Linux console, and see if that shows the diamond-like glyph or the \Unnnn thing. If it's the latter, it means the console doesn't support that character, and we cannot send its code from Emacs. We should instead send something else (provided that someone submits patches to send that "something").