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: Sat, 01 Oct 2022 09:03:37 +0300 [thread overview]
Message-ID: <835yh4cc7a.fsf@gnu.org> (raw)
In-Reply-To: <E1oeRlR-0002Pp-N4@fencepost.gnu.org> (message from Richard Stallman on Fri, 30 Sep 2022 21:58:01 -0400)
> Cc: 58159@debbugs.gnu.org
> From: Richard Stallman <rms@gnu.org>
> Date: Fri, 30 Sep 2022 21:58:01 -0400
>
> Do we really want to complicate Emacs to support the Wancho script?
The script was already supported: we automatically add support for all
the scripts defined by the Unicode Standard when we import each new
version of Unicode, simply by virtue of supporting the character
codepoints of that script.
The change in question just defined a new language-environment (a
small addition to an existing data structure) and a new (and very
simple) input method. So my conclusion (and I asked myself the same
questions when reviewing the patch) was that adding this doesn't
complicate Emacs in any significant way.
prev parent reply other threads:[~2022-10-01 6:03 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
2022-10-01 6:03 ` Eli Zaretskii [this message]
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=835yh4cc7a.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).