From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55439@debbugs.gnu.org,
"समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>,
rms@gnu.org
Subject: bug#55439: [PATCH] Add support for the Modi script
Date: Wed, 18 May 2022 18:55:25 +0530 [thread overview]
Message-ID: <87ilq3ug56.fsf@gmail.com> (raw)
In-Reply-To: <83bkvvf1qz.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 18 May 2022 15:45:24 +0300")
[புதன் மே 18, 2022] Eli Zaretskii wrote:
>> From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
>> Date: Wed, 18 May 2022 05:44:30 +0530
>> Cc: Visuwesh <visuweshm@gmail.com>, 55439@debbugs.gnu.org,
>> Eli Zaretskii <eliz@gnu.org>
>>
>> I agree that this change is correct, but let's not ever delete the old
>> name "Hindi". Keeping an old alias does no harm.
>>
>> Hindi is not an alias, it is an incorrect term.
>> No one is using Hindi to refer to the Devanagari script, therefore I think it should not be readded.
>
> AFAIU, Hindi is one language that uses the Devanagari script. Is this
> correct?
Indeed, Hindi is one of the languages that use the Devanagari script.
> If that is correct, how about having two lines in HELLO: one that
> says "Hindi" and shows a Hindi greeting, and another that says
> "Devanagari" and shows a greeting in some other language that uses
> Devanagari?
The problem here is that most of the North Indian language greetings are
"Namaskar" or "Namaste" (which is what the "Devanagari" greeting is
currently). But I maybe mistaken since I do not really know any of the
North Indian languages; my knowledge of Hindi is superficial at best.
Either way, I will ask for a greeting in Marathi, which uses the
Devanagari script as well.
>> 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 feel like 11 years is enough time.
>
> In Emacs, 11 years is nowhere near "long enough".
>
> And anyway, the script will not be renamed, since we follow Unicode in
> script names. The patch didn't rename the script, and rightfully so.
>
>> Only two functions are changed where it affects the user, both are
>> input methods: odia-itrans and
>> odia-inscript.
>
> As I wrote in the review of the patch, we cannot suddenly remove input
> methods that we had for 20 years. We must find a less drastic
> solution.
next prev parent reply other threads:[~2022-05-18 13:25 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 [this message]
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
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=87ilq3ug56.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).