unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: 55439@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, rms@gnu.org
Subject: bug#55439: [PATCH] Add support for the Modi script
Date: Wed, 18 May 2022 20:53:36 +0530	[thread overview]
Message-ID: <CAOR1sLw5UJ9ZUzP+xZ-S3sB0MNA6YOiFS=z2NVfuXjyvC-Vy6g@mail.gmail.com> (raw)
In-Reply-To: <87ee0qvpuq.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

>
> I'm not sure if using "Ram Ram" is exactly a good idea since it has
> religious implications.
>

Yes, it is religious, but I argue it is no more religious than the Spanish
"Adios", French "Adieu" or the English "Goodbye".
Religion plays a huge part in culture, so it is natural that it will also
have its impact on the words.

On Wed, May 18, 2022 at 8:40 PM Visuwesh <visuweshm@gmail.com> wrote:

> [புதன் மே 18, 2022] समीर सिंह Sameer Singh wrote:
>
> >[...]
> >  Either way, I will ask for a greeting in Marathi, which uses the
> >  Devanagari script as well.
> >
> > Marathi also uses Namsakaar.
> >
>
> I figured that would be the case.
>
> > Of course there are also local greetings, so one solution is to use the
> standard greetings in Devanagari
> > and local ones in Hindi, like रामराम (raam raam), पायलागू (paay lagu)
> etc.
>
> I'm not sure if using "Ram Ram" is exactly a good idea since it has
> religious implications.
> [ There was a thread about where we should draw the line with matters
>   like these in emacs-devel recently as well.  ]
>

[-- Attachment #2: Type: text/html, Size: 1716 bytes --]

  reply	other threads:[~2022-05-18 15:23 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 [this message]
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='CAOR1sLw5UJ9ZUzP+xZ-S3sB0MNA6YOiFS=z2NVfuXjyvC-Vy6g@mail.gmail.com' \
    --to=lumarzeli30@gmail.com \
    --cc=55439@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rms@gnu.org \
    --cc=visuweshm@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 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).