From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Unicode fonts - Re: Why do I find ^L in elisp code?
Date: Mon, 24 May 2021 21:05:28 +0300 [thread overview]
Message-ID: <YKvq6Pd26q+e/3uZ@protected.localdomain> (raw)
In-Reply-To: <837djodvja.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2021-05-24 18:03]:
> > Date: Mon, 24 May 2021 17:24:54 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> >
> > These letters like 𝐦𝐚𝐭𝐡𝐞𝐦𝐚𝐭𝐢𝐜𝐚𝐥 𝐛𝐨𝐥𝐝 should be supported by every
> > English screen reader, regardless
>
> How far are you prepared to go with these ridiculous "should be
> supported" requirements?
That is up to screen reader authors to decide. Language is ever
changing. Before some decades we did not have computer for language
development, now we have it. Meanings are everywhere. It is up to
screen reader to try to decipher such meanings.
Just as the language is constantly adapting and changing to reflect
our changing lives, experiences and culture, so do the written and
digital symbols by which we express various meanings.
Example is for word 𝗳𝘂𝗻𝗻𝘆 expressed with mathematial sans-serif bold
Unicode chars that gives us 9000+ results on Bing.com:
https://www.bing.com/search?q=%f0%9d%97%b3%f0%9d%98%82%f0%9d%97%bb%f0%9d%97%bb%f0%9d%98%86&search=&first=61&FORM=PERE5
Humans do express meanings by using mathematical sans-serif bold
Unicode, including all other possible Unicode characters, bill𝗶ons of
times.
Combinations are many, it is not easy work, it is up to authors to
decide what to support, and what not.
> Would you also like "реасе" to be supported by English screen
> readers, for example?
Definitely, just that I don't understand the meaning of your
question. Do you mean that piece and peace would be spoken same? Do
you think the ☮?
Good screen readers should be built-in into OS, be part of the OS, and
they should by default support all languages on the planet wherever OS
is distributed. Because we don't work organized as ants, we may never
accomplish such goal, we work as human.
> You are judging characters by their appearance, which is incorrect.
Yes, surely I understand it may be technically incorrect, though
humanely it gives a style even in those cases where text style cannot
be otherwise assigned. For example in search engines, email subjects,
social media interactions, and so on. The 9000 search results show
that 9000 authors most probably don't even know that those Latin
characters have some other purposes. The trend will continue, in few
years it will be maybe 50000 results or 100,000 results, all with
meanings easily interpreted by humans. Screen reader authors may
decide to support such.
> Characters should be judged by their codepoints and their
> attributes, not by how they look in some particular font.
(•◡•) Maybe yes, maybe yes, but we cannot tell that to thousands of
people who already use it. Language is changing, written language is
also changing. People communicate.
In terms of a program if there is nothing mathematical and program
finds several let us say mathematical bold Unicode characters, that
program can replace it with normal letters and read as such. It is
also possible to recognize if letters belong to the English language
before reading it.
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/
next prev parent reply other threads:[~2021-05-24 18:05 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 14:53 Why do I find ^L in elisp code? Christopher Dimech
2021-05-22 15:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 15:12 ` Christopher Dimech
2021-05-22 15:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 19:14 ` [External] : " Drew Adams
2021-05-22 15:15 ` Eli Zaretskii
2021-05-22 15:17 ` Omar Polo
2021-05-22 15:22 ` 2QdxY4RzWzUUiLuE
2021-05-22 15:30 ` arthur miller
2021-05-22 15:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 15:47 ` Christopher Dimech
2021-05-22 15:58 ` Omar Polo
2021-05-22 16:51 ` arthur miller
2021-05-22 19:15 ` [External] : " Drew Adams
2021-05-22 16:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 16:18 ` 2QdxY4RzWzUUiLuE
2021-05-22 16:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 16:43 ` 2QdxY4RzWzUUiLuE
2021-05-22 17:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 16:27 ` arthur miller
2021-05-22 17:32 ` Christopher Dimech
2021-05-22 18:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 18:32 ` Christopher Dimech
2021-05-22 18:40 ` music with/from Emacs (was: Re: Why do I find ^L in elisp code?) Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 21:09 ` music with/from Emacs Arthur Miller
2021-05-22 21:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 21:53 ` Arthur Miller
2021-05-22 21:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-24 1:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-24 11:44 ` Arthur Miller
2021-05-22 16:33 ` Why do I find ^L in elisp code? Jean Louis
2021-05-22 17:02 ` Eduardo Ochs
2021-05-22 20:08 ` Jean Louis
2021-05-22 20:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 20:25 ` Jean Louis
2021-05-23 6:42 ` Eli Zaretskii
2021-05-23 19:14 ` Unicode fonts - " Jean Louis
2021-05-23 19:42 ` Input method generator package - Re: Unicode fonts Jean Louis
2021-05-24 8:00 ` Unicode fonts - Re: Why do I find ^L in elisp code? Yuri Khan
2021-05-24 8:18 ` Christopher Dimech
2021-05-24 8:48 ` Jean Louis
2021-05-24 9:38 ` Christopher Dimech
2021-05-24 14:06 ` Yuri Khan
2021-05-24 14:24 ` Jean Louis
2021-05-24 14:36 ` Yuri Khan
2021-05-24 17:39 ` Jean Louis
2021-05-24 15:02 ` Eli Zaretskii
2021-05-24 17:31 ` Christopher Dimech
2021-05-24 18:05 ` Jean Louis [this message]
2021-05-24 18:12 ` Eli Zaretskii
2021-05-24 20:19 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YKvq6Pd26q+e/3uZ@protected.localdomain \
--to=bugs@gnu.support \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).