unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55493@debbugs.gnu.org, Visuwesh <visuweshm@gmail.com>
Subject: bug#55493: [PATCH] Rename Oriya to Odia
Date: Wed, 18 May 2022 21:50:13 +0530	[thread overview]
Message-ID: <CAOR1sLxQzEdqziLnxmypynStMr52LKvNOjEDC6CHEN6TEMr0Uw@mail.gmail.com> (raw)
In-Reply-To: <83v8u2esuv.fsf@gnu.org>

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

>
> By "input system", do you mean a separate language-environment with a
> separate input method?  That would be OK, I think


I meant to say, "input method".
Is there a need for a separate language-environment?
I think only writing a new input-method  will be sufficient, right?

On Wed, May 18, 2022 at 9:27 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> > Date: Wed, 18 May 2022 21:08:09 +0530
> > Cc: Visuwesh <visuweshm@gmail.com>, 55493@debbugs.gnu.org
> >
> >  The changes to HELLO do more that the above says.  I don't think I
> >  understand the reason for the change in the "South Asia" line.
> >
> > The South Asia line was correcting the Odia greeting, which I had
> changed previously (from "Listen" to
> > "Namaskaar")
>
> Please reflect that in the log message.
>
> >  This is unrelated, and I see no reason to rename the variable in a
> >  backward-incompatible way.  It's just a variable, so it doesn't have
> >  to be named rigorously correct.  If we were discussing new code, the
> >  correction would have had its place, but not now, 16 years after it
> >  was introduced.
> >
> > This variable name is somewhat misleading. When I searched "iso 638",
> online to see whether the language
> > codes were updated or not,
> >  it showed me results for oven boards, later when searching "iso 638
> languages" I realized that the correct
> > standard number is 639.
> > There was also a FIXME above it, so I fixed that.
> > If there is a backward-compatible way to change it please tell me, or if
> you still feel the change is not
> > warranted, I will revert this it.
>
> A backward-compatible change would need to introduce an obsolete alias
> with the old name.
>
> >  I don't think we should rename variables and functions.  It's just a
> >  lot of hassle for us (defalias etc.) and potentially for others, and
> >  the gain is very small.  This variable doesn't even say "oriya", just
> >  "ori".  Let's not be too radical here.
> >
> > Then I should only rename in etc/HELLO, and in (set-language-info-alist)
> of lisp/language/indian.el.
>
> Yes, I think so.
>
> >  We cannot rename an input method we had for almost 20 years.  If there
> >  is some way of having an alias for an input method (I don't think so,
> >  but maybe I'm missing something), let's use that; otherwise we will
> >  have either to leave the old name alone or define a new input method
> >  that is an exact copy of the old one, except for the name and the
> >  mode-line indicator.
> >
> > How about I make a new Odia input system, just like the ones which I had
> made for the other scripts, and
> > leave the old ones alone?
>
> By "input system", do you mean a separate language-environment with a
> separate input method?  That would be OK, I think.
>
> Thanks.
>

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

  reply	other threads:[~2022-05-18 16:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 23:56 bug#55493: [PATCH] Rename Oriya to Odia समीर सिंह Sameer Singh
2022-05-18  4:27 ` Visuwesh
2022-05-18 12:47   ` Eli Zaretskii
2022-05-18 15:38     ` समीर सिंह Sameer Singh
2022-05-18 15:57       ` Eli Zaretskii
2022-05-18 16:20         ` समीर सिंह Sameer Singh [this message]
2022-05-18 16:50           ` Eli Zaretskii
2022-05-18 20:32             ` समीर सिंह Sameer Singh
2022-05-19 12:36               ` Eli Zaretskii
2022-05-19 19:34                 ` समीर सिंह Sameer Singh
2022-05-18 12:34 ` Eli Zaretskii
2022-05-19 23:13   ` Richard Stallman
2022-05-19 23:21     ` समीर सिंह Sameer Singh
2022-05-20  6:54     ` Eli Zaretskii
2022-05-21 22:47       ` Richard Stallman

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=CAOR1sLxQzEdqziLnxmypynStMr52LKvNOjEDC6CHEN6TEMr0Uw@mail.gmail.com \
    --to=lumarzeli30@gmail.com \
    --cc=55493@debbugs.gnu.org \
    --cc=eliz@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).