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.tangents Subject: Re: Display of undisplayable characters: \U01F3A8 instead of diamond Date: Sat, 03 Sep 2022 03:41:32 +0200 Message-ID: <87bkrxxmib.fsf@dataswamp.org> References: <2f302d1c3966849477b3@heytings.org> <83mtbiovzr.fsf@gnu.org> <83a67hq3l7.fsf@gnu.org> <878rn1zk52.fsf@dataswamp.org> <2b564d99d3a09e73c98e@heytings.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="1016"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: emacs-tangents@gnu.org Cancel-Lock: sha1:4/1nNw2waHyrnobDR8J1tQ4lGKo= Original-X-From: emacs-tangents-bounces+get-emacs-tangents=m.gmane-mx.org@gnu.org Sat Sep 03 07:59:56 2022 Return-path: Envelope-to: get-emacs-tangents@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 1oUMCC-000AcN-R4 for get-emacs-tangents@m.gmane-mx.org; Sat, 03 Sep 2022 07:59:56 +0200 Original-Received: from localhost ([::1]:37192 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oUMCB-0002Q2-OX for get-emacs-tangents@m.gmane-mx.org; Sat, 03 Sep 2022 01:59:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55330) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oUIAK-00047Y-TN for emacs-tangents@gnu.org; Fri, 02 Sep 2022 21:41:44 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:54936) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oUIAI-0007N0-Rx for emacs-tangents@gnu.org; Fri, 02 Sep 2022 21:41:44 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1oUIAF-0001Wm-6d for emacs-tangents@gnu.org; Sat, 03 Sep 2022 03:41:39 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-tangents@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=get-emacs-tangents@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.25, 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-Mailman-Approved-At: Sat, 03 Sep 2022 01:55:36 -0400 X-BeenThere: emacs-tangents@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-tangents-bounces+get-emacs-tangents=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-tangents" Xref: news.gmane.io gmane.emacs.tangents:911 Archived-At: Gregory Heytings wrote: >> I don't see any failure. Richard's complaint was that >> characters without glyphs were getting displayed as long >> hex strings rather than the "diamond" that they were >> previously displayed as. I think the complaint has merit. >> It seems to me to be a classic case for a user option. > > You forget to mention that the context in which this bug was > fixed in January is that RMS complained that ligatures such > as "fi" showed up as a diamond [...] At that time what he > wanted is that Emacs would automatically replace such > ligatures by two letters in his Linux console, and that's > what he got: Eli improved the latin1-display-ucs-per-lynx > function in fd42ba3adb. At that time diamonds were > considered "unhelpful", and he said for example: "I doubt > any user wants to see a diamond instead of `fi'." > > During that discussion, the bug that is now objected against > was also fixed, by 10c680551e. > > I, too, doubt any user wants to see a diamond instead of an > actual character! Why are these diamonds suddenly useful > again? How comes that a proposed solution with which > ligatures such as "fi" are actually displayed as "fi", with > which UTF-8 is actually supported instead of having to > resort to ugly hacks such as latin1-display-ucs-per-lynx, > and with which missing glyphs are in fact again displayed > with these same diamonds, is criticized? Guys, we are not fighting a holy war over in what order to make the Sign of the Cross here, right? -- underground experts united https://dataswamp.org/~incal