all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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, 15 Oct 2022 09:35:30 +0300	[thread overview]
Message-ID: <83r0z97fwt.fsf@gnu.org> (raw)
In-Reply-To: <E1ojSAi-0000wQ-7U@fencepost.gnu.org> (message from Richard Stallman on Fri, 14 Oct 2022 17:24:48 -0400)

> From: Richard Stallman <rms@gnu.org>
> Cc: eliz@gnu.org, 58159@debbugs.gnu.org
> Date: Fri, 14 Oct 2022 17:24:48 -0400
> 
>   > This is what a typical patch for adding a script in Emacs looks like:
>   > 1. A one line entry in etc/NEWS announcing the support of the script and
>   > its language environment.
>   > 2. A one line greeting in the language/script which is added in etc/HELLO
>   > (optional)
>   > 3. A one line entry in script-representative-chars in
>   > lisp/international/fontset.el so that Emacs can select an appropriate font
>   > for it.
>   > 4. Adding the script name in setup-default-fontset in
>   > lisp/international/fontset.el
>   > 5. Defining a language environment for the script in the lisp/language/*.el
>   > files which includes the following entries:
>   > its charset (usually unicode), its coding-system (usually utf-8), its
>   > coding-priority (usually utf-8), its input-method, its sample text (the
>   > same text which is added in etc/HELLO),
>   > a one line documentation usually in the following template: "foo language
>   > and its script bar are supported in this language environment."
>   > 6. Adding composition rules for the script (optional, only needed for
>   > complex scripts)
>   > 7. Adding an input-method for the script in lisp/leim/quail/*.el files
> 
> That looks like nontrivial work to add each script.
> Not a big job, but not minimal either.

Only the two last items are nontrivial.  And item 6 is only necessary
for some scripts.  All the rest is basically trivial boilerplate.

> For a script that users actually want, it is work worth doing.
> For a script that we support only because some bureaucrats
> decided to include it in Unicode, is it worth that much?

We cannot control which itches our contributors want to scratch.
Letting them scratch their itches is an important aspect of being able
to keep them contributing to Emacs in all other areas.  This
particular itch is useful to Emacs, so I see no reason to object their
scratching it.





  reply	other threads:[~2022-10-15  6:35 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 [this message]
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=83r0z97fwt.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.