From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: lumarzeli30@gmail.com, 58159@debbugs.gnu.org
Subject: bug#58159: [PATCH] Add support for the Wancho script
Date: Mon, 03 Oct 2022 05:38:02 +0300 [thread overview]
Message-ID: <83bkqtzl6d.fsf@gnu.org> (raw)
In-Reply-To: <E1of9uM-0004q6-LB@fencepost.gnu.org> (message from Richard Stallman on Sun, 02 Oct 2022 21:06:10 -0400)
> Cc: 58159@debbugs.gnu.org
> From: Richard Stallman <rms@gnu.org>
> Date: Sun, 02 Oct 2022 21:06:10 -0400
>
> But if Unicode is inclined to do things like this, how many more
> barely-used scripts will it adopt? How many more has it already
> adopted?
That is not our question to answer. The Unicode Consortium makes
these decisions based on their criteria. We just support the
characters they add.
These additions are usually so minor that I believe they don't warrant
any discussion. E.g., part of the support for new characters is the
ability to up-case and down-case them; we lift the data from the
Unicode Character Database, which we import. It would be unthinkable
for Emacs not to be able to do these simple text operations on any
character.
next prev parent reply other threads:[~2022-10-03 2:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 11:07 bug#58159: [PATCH] Add support for the Wancho script समीर सिंह Sameer Singh
2022-09-29 11:09 ` समीर सिंह Sameer Singh
2022-09-29 13:15 ` Eli Zaretskii
2022-09-29 13:21 ` समीर सिंह Sameer Singh
2022-09-29 14:27 ` Robert Pluim
2022-09-29 15:19 ` समीर सिंह Sameer Singh
2022-09-29 15:41 ` Robert Pluim
2022-10-01 1:58 ` Richard Stallman
2022-10-01 4:53 ` समीर सिंह Sameer Singh
2022-10-03 1:06 ` Richard Stallman
2022-10-03 2:38 ` Eli Zaretskii [this message]
2022-10-08 22:35 ` Richard Stallman
2022-10-09 1:08 ` समीर सिंह Sameer Singh
2022-10-14 21:24 ` Richard Stallman
2022-10-15 6:35 ` Eli Zaretskii
2022-10-09 4:22 ` Eli Zaretskii
2022-10-01 6:03 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bkqtzl6d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58159@debbugs.gnu.org \
--cc=lumarzeli30@gmail.com \
--cc=rms@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.