From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: Unicode fonts - Re: Why do I find ^L in elisp code? Date: Mon, 24 May 2021 17:24:54 +0300 Message-ID: References: <87im3a5xqc.fsf@zoho.eu> <83h7iuj6i1.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="5888"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0.6 (2021-03-06) Cc: help-gnu-emacs To: Yuri Khan Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon May 24 16:40:02 2021 Return-path: Envelope-to: geh-help-gnu-emacs@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 1llBkP-0001F6-5V for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 24 May 2021 16:40:01 +0200 Original-Received: from localhost ([::1]:35014 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1llBkO-0004kT-2k for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 24 May 2021 10:40:00 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42440) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1llBYv-0006WZ-Kv for help-gnu-emacs@gnu.org; Mon, 24 May 2021 10:28:10 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:42931) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1llBYl-0002hU-Hv for help-gnu-emacs@gnu.org; Mon, 24 May 2021 10:28:08 -0400 Original-Received: from localhost ([::ffff:102.87.235.181]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 00000000000AE2D6.0000000060ABB7EB.00001FE7; Mon, 24 May 2021 07:27:55 -0700 Mail-Followup-To: Yuri Khan , help-gnu-emacs Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:130184 Archived-At: * Yuri Khan [2021-05-24 17:08]: > On Mon, 24 May 2021 at 15:52, Jean Louis wrote: > > > Social media is full of ◦•●♡ £åñ¢¥ Lꆆêr§ ♡●•◦ beyond the built-in > > features. > > > > There is no need to constrain people in using Unicode symbols > > regardless for what they are meant. People may like symbols regardless > > of their meanings or political or scientific purposes. > > No, but we can feel morally justified to say they do it wrong by > making their posts less accessible for users (1) without font coverage > for those blocks; (2) of less capable displays such as out-of-the-box > Linux console; (3) of Braille displays; (4) of screen readers. In social media, it their individual expression and creators need not think how other people will perceive it, or not be able to perceive it. Computer program that read text should be programmed not robotically, rather humanely and know how to interpret such characters not in a robotical way, but in human kind of a way. These letters like 𝐦𝐚𝐭𝐡𝐞𝐦𝐚𝐭𝐢𝐜𝐚𝐥 𝐛𝐨𝐥𝐝 should be supported by every English screen reader, regardless, as those are letters of English alphabet. But English class of a screen reader would not support plethora of other alphabets for the rest of the world as they are not same chars as English chars, let us just mention Cyrillic here. So it is really up to screen reader to support it, not to the user to conform oneself to limitations of other people's software. A screen reader that does not understand some characters is lacking features. Character like ⌣ should be supported as "smile" by screen reader as it is what it really represents, then there is plethora of other Unicode characters even more suitable for screen readers and Braille displays then what letters are. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns Sign an open letter in support of Richard M. Stallman https://stallmansupport.org/