unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: 55439@debbugs.gnu.org, lumarzeli30@gmail.com, eliz@gnu.org
Subject: bug#55439: [PATCH] Add support for the Modi script
Date: Wed, 18 May 2022 10:03:46 +0530	[thread overview]
Message-ID: <87sfp7v4r9.fsf@gmail.com> (raw)
In-Reply-To: <E1nr69o-0006EV-Ro@fencepost.gnu.org> (Richard Stallman's message of "Tue, 17 May 2022 18:59:12 -0400")

[செவ்வாய் மே 17, 2022] Richard Stallman wrote:

> [[[ 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. ]]]
>
>   > While we are it, should we change all instances of "Oriya" in Emacs to
>   > "Odiya"?
>
> The old name has been in use for almost a century, if not more, so we
> should not rush to deprecate it.  Perhaps in 30 years.
>
> Until then, let's make sure that both the old name and the new name
> are accepted, in any places in which people can input the name of a
> script.

I agree that both the new and the old name should be accepted, but I am
not sure it is worth the trouble.  In the interest of serving users, I
think it is better if we do the rename and inconvenience others a tiny
bit.  I would say that the current name "Oriya" makes it hard to find
the Emacs facilities of Odia support harder to find/learn as the user
might not think about searching for the old name.  Also, I believe the
rename will give a certain empowerment to the native speakers; much like
the renaming of cities and towns that has happened/is happening now in
India.





  parent reply	other threads:[~2022-05-18  4:33 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 23:33 bug#55439: [PATCH] Add support for the Modi script समीर सिंह Sameer Singh
2022-05-16  7:00 ` Pankaj Jangid
2022-05-17 22:57   ` Richard Stallman
2022-05-16 11:33 ` Eli Zaretskii
2022-05-16 23:25   ` समीर सिंह Sameer Singh
2022-05-17  9:49     ` Visuwesh
2022-05-17  9:57       ` समीर सिंह Sameer Singh
2022-05-17 12:11         ` Eli Zaretskii
2022-05-17 13:42           ` Visuwesh
2022-05-17 13:48             ` Visuwesh
2022-05-17 16:04               ` Eli Zaretskii
2022-05-17 16:05             ` Eli Zaretskii
2022-05-17 12:10       ` Eli Zaretskii
2022-05-17 14:10         ` Visuwesh
2022-05-17 16:06           ` Eli Zaretskii
2022-05-17 14:14         ` Visuwesh
2022-05-17 22:59       ` Richard Stallman
2022-05-18  0:14         ` समीर सिंह Sameer Singh
2022-05-18  3:08           ` Pankaj Jangid
2022-05-18  3:41             ` समीर सिंह Sameer Singh
2022-05-18  7:12               ` Pankaj Jangid
2022-05-18 12:51                 ` Eli Zaretskii
2022-05-19  3:14                   ` Pankaj Jangid
2022-05-19  7:12                     ` Eli Zaretskii
2022-05-19 13:40                       ` Pankaj Jangid
2022-05-19 13:58                         ` Eli Zaretskii
2022-05-19 14:31                           ` Visuwesh
2022-05-19 15:52                             ` Eli Zaretskii
2022-05-19 16:32                               ` Pankaj Jangid
2022-05-21  8:06                                 ` Eli Zaretskii
2022-05-18 12:47               ` Eli Zaretskii
2022-05-18 12:45           ` Eli Zaretskii
2022-05-18 13:25             ` Visuwesh
2022-05-18 13:33               ` Eli Zaretskii
2022-05-18 14:58                 ` समीर सिंह Sameer Singh
2022-05-18 15:10                   ` Visuwesh
2022-05-18 15:23                     ` समीर सिंह Sameer Singh
2022-05-19 23:13                       ` Richard Stallman
2022-05-18 15:47                   ` Eli Zaretskii
2022-05-18 16:15                     ` समीर सिंह Sameer Singh
2022-05-18  4:33         ` Visuwesh [this message]
2022-05-19 23:13           ` Richard Stallman
2022-05-17 13:24     ` 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

  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=87sfp7v4r9.fsf@gmail.com \
    --to=visuweshm@gmail.com \
    --cc=55439@debbugs.gnu.org \
    --cc=eliz@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).