all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
Cc: eliz@gnu.org, 58159@debbugs.gnu.org
Subject: bug#58159: [PATCH] Add support for the Wancho script
Date: Fri, 14 Oct 2022 17:24:48 -0400	[thread overview]
Message-ID: <E1ojSAi-0000wQ-7U@fencepost.gnu.org> (raw)
In-Reply-To: <CAOR1sLwiq+ixOQ-70HzsUGTw6z6SGV0x9zr9cFrCugAXJAdRGQ@mail.gmail.com> (message from समीर सिंह Sameer Singh on Sun, 9 Oct 2022 06:38:53 +0530)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Can you elaborate on what changes are needed in which manual?

I don't know, but normally every new addition calls for documentation
somewhere.

  > 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.

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?

  > These scripts were not developed for "PR motives", they were developed to
  > serve the needs of the community.

What I've read suggests the opposite.  I am not convinced that the
community experienced or experiences such linguistic "needs".  It
looks like some activists in that community decided that using their
own script would help them get political benefits, so they push for
its adoption.

What we know about this is sketchy.  (I could see only fragments of
the article you pointed at -- I suspect nonfree JS blocks the rest.)

If the speakers of a language are really using a script, I am in favor
of supporting it.

  > It is necessary for Unicode to support them because this is not the age of
  > pen and paper where the only thing limiting you to write any script for
  > communication is... you.

I don't subscribe to the idea that we Emacs developers _must_ support
every script that a minority of some speecdh community campaigns to
switch to.  That is dogmatic, and it could impose an unlimited burden
on us.  If every endangered language gets its own script, that could
be almost 200 more scripts coming from India alone.

I am in favor of preserving endangered languages, but that doesn't
usually require inventing a new script for each one.  For instance,
speakers of 22 Maya languages got together and established a rather
natural convention for writing them in the Latin alphabet.  The
convention states how to express each sound used in any of those
languages.  You can find it in Maya Languages in Wikipedia.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  reply	other threads:[~2022-10-14 21:24 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 [this message]
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=E1ojSAi-0000wQ-7U@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=58159@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=lumarzeli30@gmail.com \
    /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.