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: Sun, 09 Oct 2022 07:22:22 +0300 [thread overview]
Message-ID: <83leppk4n5.fsf@gnu.org> (raw)
In-Reply-To: <E1ohIPw-0008J7-2h@fencepost.gnu.org> (message from Richard Stallman on Sat, 08 Oct 2022 18:35:36 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: lumarzeli30@gmail.com, 58159@debbugs.gnu.org
> Date: Sat, 08 Oct 2022 18:35:36 -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.
>
> They are questions about the future, so we cannot look for answers
> today. But they do affect what our attitude towards Unicode should
> be.
Emacs supports all the characters defined by Unicode. This design is
from Emacs 23 onwards. So any characters Unicode adds will be
supported by Emacs as soon as we import the latest character database.
next prev parent reply other threads:[~2022-10-09 4:22 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
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 [this message]
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=83leppk4n5.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.