From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58376@debbugs.gnu.org, Visuwesh <visuweshm@gmail.com>
Subject: bug#58376: [PATCH] Set the PARENTS argument for language environments
Date: Sun, 30 Oct 2022 16:01:35 +0530 [thread overview]
Message-ID: <CAOR1sLxuAU6e0ikMw0t6gKHhA_5ofBiYuH2YAUi8WxoHD=m-+g@mail.gmail.com> (raw)
In-Reply-To: <83pme9fwa5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
Yes, that would be okay too.
On Sun, Oct 30, 2022, 3:50 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> > Date: Sun, 30 Oct 2022 15:00:44 +0530
> > Cc: 58376@debbugs.gnu.org, visuweshm@gmail.com
> >
> > However, the second part of those patches makes little sense to me: if
> > these languages are considered to be part of "Indian" languages, why
> > leave them in "Misc"? "Misc" is for languages that have no "parent"
> > family.
> >
> > Kharoshthi is different from the Brahmic scripts in that it is not
> derived from Brahmi but instead from Aramaic.
> > It was also used in regions not present in modern India.
> > But it was used to write Indian languages, therefore it made sense to me
> to include it in both Indian and Misc.
>
> I'm okay with "Indian". It's "Misc" that I question. Would it be
> okay to have these only in "Indian"?
>
[-- Attachment #2: Type: text/html, Size: 1568 bytes --]
next prev parent reply other threads:[~2022-10-30 10:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 11:12 bug#58376: [PATCH] Set the PARENTS argument for language environments समीर सिंह Sameer Singh
2022-10-08 11:15 ` समीर सिंह Sameer Singh
2022-10-08 14:46 ` Eli Zaretskii
2022-10-08 16:18 ` समीर सिंह Sameer Singh
2022-10-08 18:16 ` Eli Zaretskii
2022-10-08 19:16 ` समीर सिंह Sameer Singh
2022-10-09 8:29 ` Eli Zaretskii
2022-10-09 10:28 ` समीर सिंह Sameer Singh
2022-10-09 13:22 ` Eli Zaretskii
2022-10-09 13:59 ` समीर सिंह Sameer Singh
2022-10-09 14:23 ` Eli Zaretskii
2022-10-09 14:46 ` समीर सिंह Sameer Singh
2022-10-09 14:55 ` Eli Zaretskii
2022-10-09 14:50 ` Visuwesh
2022-10-09 15:06 ` Visuwesh
2022-10-09 15:30 ` Visuwesh
2022-10-10 14:06 ` समीर सिंह Sameer Singh
2022-10-10 14:32 ` Visuwesh
2022-10-10 14:38 ` समीर सिंह Sameer Singh
2022-10-10 15:59 ` Visuwesh
2022-10-10 18:38 ` समीर सिंह Sameer Singh
2022-10-30 8:22 ` समीर सिंह Sameer Singh
2022-10-30 8:43 ` Eli Zaretskii
2022-10-30 9:30 ` समीर सिंह Sameer Singh
2022-10-30 10:20 ` Eli Zaretskii
2022-10-30 10:31 ` समीर सिंह Sameer Singh [this message]
2022-10-30 11:18 ` Eli Zaretskii
2022-10-30 11:19 ` समीर सिंह Sameer Singh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOR1sLxuAU6e0ikMw0t6gKHhA_5ofBiYuH2YAUi8WxoHD=m-+g@mail.gmail.com' \
--to=lumarzeli30@gmail.com \
--cc=58376@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.