unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Stefan Baums <baums@stefanbaums.com>
Cc: 55539@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#55539: 28.1; Support for the Kharoṣṭhī Script
Date: Wed, 8 Jun 2022 18:59:08 +0530	[thread overview]
Message-ID: <CAOR1sLznpNeJ99XVh4rGneORSWM5cHUx02Dq+0vY=aDbe4-82w@mail.gmail.com> (raw)
In-Reply-To: <87mter54po.fsf@stefanbaums.com>

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

>The convention among those working with it is to use diacritics,
>so I opted for that in the visible name of the script, but for the
>(or rather, a) form without diacritics in file names and code.


> If this is a more correct way, should the others be changed as
> well?

>That is not up to me to decide, but I would not be opposed to
>“Brāhmī” for parallelism.


> Also I noticed that Kharoṣṭhī and Gāndhārī are written in IAST
> but not Saṃskṛta.

>The difference here is that “Sanskrit” is much more part of the
>English language (in dictionaries etc.) than “Kharoṣṭhī” and
>“Brāhmī.”

The issue I had was this naming scheme was inconsistent with the previous
ones, but of course it is your patch you can do as you prefer, I have no
strong inclinations either way.


> since now there is also a misc-lang.el in lisp/leim/quail/ I
> think the Kharoshthi input method should be moved there.

>I had a look. That file is billed as

   >Quail package for inputting Miscellaneous characters

>which is a bit of misnomer, as it only contains input rules for
>the Hanifi Rohingya script. Why did you not give that script its
>own input file, as has been the practice so far?

This is because lisp/leim/quail/misc-lang.el is a recently created file, I
have plans to include more input methods there, such as, Avestan, Gothic,
Shavian, Desert, Imperial Aramaic etc.
>Also because the Kharoṣṭhī rules are quite numerous, I would
>prefer for them to stay in their own file.

I understand.

Thanks.



सोम, 6 जून 2022, 12:15 am को Stefan Baums <baums@stefanbaums.com> ने लिखा:

> > Great! The Kharoshthi script is finally being included in Emacs!
>
> Thank you. About time, isn’t it?
>
> > Should Kharoshthi be written with diacritics? I know Kharoṣṭhī
> > is more correct way to write it, but other Indic scripts are
> > written without it.
>
> The convention among those working with it is to use diacritics,
> so I opted for that in the visible name of the script, but for the
> (or rather, a) form without diacritics in file names and code.
>
> > If this is a more correct way, should the others be changed as
> > well?
>
> That is not up to me to decide, but I would not be opposed to
> “Brāhmī” for parallelism.
>
> > Also I noticed that Kharoṣṭhī and Gāndhārī are written in IAST
> > but not Saṃskṛta.
>
> The difference here is that “Sanskrit” is much more part of the
> English language (in dictionaries etc.) than “Kharoṣṭhī” and
> “Brāhmī.”
>
> > since now there is also a misc-lang.el in lisp/leim/quail/ I
> > think the Kharoshthi input method should be moved there.
>
> I had a look. That file is billed as
>
>    Quail package for inputting Miscellaneous characters
>
> which is a bit of misnomer, as it only contains input rules for
> the Hanifi Rohingya script. Why did you not give that script its
> own input file, as has been the practice so far?
>
> Also because the Kharoṣṭhī rules are quite numerous, I would
> prefer for them to stay in their own file.
>

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

  reply	other threads:[~2022-06-08 13:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  9:48 bug#55539: 28.1; Support for the Kharoṣṭhī Script Stefan Baums
2022-05-20 16:18 ` Eli Zaretskii
2022-05-20 17:16   ` Stefan Baums
2022-05-20 17:27     ` Eli Zaretskii
2022-05-20 18:05     ` Stefan Baums
2022-05-31 13:47     ` Eli Zaretskii
2022-06-05 16:55       ` Stefan Baums
2022-06-05 16:58         ` Eli Zaretskii
2022-06-05 17:18           ` Stefan Baums
2022-06-05 17:52             ` समीर सिंह Sameer Singh
2022-06-05 18:45               ` Stefan Baums
2022-06-08 13:29                 ` समीर सिंह Sameer Singh [this message]
2022-06-08 18:42                   ` Stefan Baums
2022-06-09  4:59                     ` Eli Zaretskii
2022-06-09  9:40                       ` Stefan Baums
2022-06-09 10:17                         ` Eli Zaretskii
2022-06-09  9:14             ` Eli Zaretskii
2022-06-09  9:52               ` Stefan Baums
2022-06-09  9:56                 ` Stefan Baums
2022-06-09 10:29                 ` Eli Zaretskii
2022-06-09 10:37                   ` Stefan Baums
2022-05-20 17:26   ` Stefan Baums

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='CAOR1sLznpNeJ99XVh4rGneORSWM5cHUx02Dq+0vY=aDbe4-82w@mail.gmail.com' \
    --to=lumarzeli30@gmail.com \
    --cc=55539@debbugs.gnu.org \
    --cc=baums@stefanbaums.com \
    --cc=eliz@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).