From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 56323@debbugs.gnu.org
Subject: bug#56323: 29.0.50; [v2] Add new customisable phonetic Tamil input method
Date: Sat, 02 Jul 2022 09:35:56 +0300 [thread overview]
Message-ID: <83o7y8c983.fsf@gnu.org> (raw)
In-Reply-To: <8735fkkvqd.fsf@gmail.com> (message from Visuwesh on Sat, 02 Jul 2022 09:32:34 +0530)
> From: Visuwesh <visuweshm@gmail.com>
> Cc: 56323@debbugs.gnu.org
> Date: Sat, 02 Jul 2022 09:32:34 +0530
>
> > Please tell what is the actual order of the characters. That is,
> > where is that order defined, and by what criteria?
>
> I'm not sure what you mean "where is that order defined," I don't think
> there is a definition per se, it just happens to be so.
>
> There are two "classes" of consonants: those that are part of Tamil
> (let's call them "core") and those borrowed from Sanskrit. When one
> writes the consonants in order, the core consonants come first then the
> Sanskrit ones. You can find the order of the core consonants in
> wikipedia here in the table titled "Tamil consonants":
> https://en.wikipedia.org/wiki/Tamil_script#Letters
>
> We need not worry too much about the order of Sanskrit consonants, we
> just need to ensure that they come after the core consonants. You can
> find these Sanskrit consonants in the table titled "Grantha consonants
> in Tamil" in the same link.
>
> I hope this is clear.
>
> As for the criteria, it is simply "Tamil consonants then the Sanskrit
> consonants."
Then your comparison function should first see whether a character is
in the former or the latter group, and use string-lessp or character
codepoint comparison with each group, right? But that's not what you
did, so I wonder whether my understanding is correct.
next prev parent reply other threads:[~2022-07-02 6:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 12:13 bug#56323: 29.0.50; Add new customisable phonetic Tamil input method Visuwesh
2022-06-30 14:08 ` Visuwesh
2022-06-30 15:53 ` Visuwesh
2022-07-01 12:59 ` bug#56323: 29.0.50; [v2] " Visuwesh
2022-07-01 13:01 ` Visuwesh
2022-07-01 13:22 ` Eli Zaretskii
2022-07-01 13:47 ` Visuwesh
2022-07-01 14:06 ` Eli Zaretskii
2022-07-01 14:30 ` Visuwesh
2022-07-01 16:09 ` Eli Zaretskii
2022-07-01 16:37 ` Visuwesh
2022-07-01 18:16 ` Eli Zaretskii
2022-07-02 4:02 ` Visuwesh
2022-07-02 6:35 ` Eli Zaretskii [this message]
2022-07-02 6:54 ` Visuwesh
2022-07-02 7:17 ` Eli Zaretskii
2022-07-02 7:35 ` Eli Zaretskii
2022-07-02 7:46 ` Eli Zaretskii
2022-07-02 8:11 ` Visuwesh
2022-07-02 8:29 ` Eli Zaretskii
2022-07-02 8:40 ` Visuwesh
2022-07-02 8:54 ` Eli Zaretskii
2022-07-02 9:33 ` Visuwesh
2022-07-02 9:38 ` Eli Zaretskii
2022-07-02 10:31 ` Visuwesh
2022-07-02 10:46 ` Eli Zaretskii
2022-07-02 12:08 ` Visuwesh
2022-07-02 11:05 ` समीर सिंह Sameer Singh
2022-07-02 12:04 ` Visuwesh
2022-07-02 12:23 ` Eli Zaretskii
2022-07-02 6:58 ` Eli Zaretskii
2022-07-02 7:58 ` Visuwesh
2022-07-02 8:39 ` Eli Zaretskii
2022-07-02 9:28 ` Visuwesh
2022-07-10 3:56 ` Visuwesh
2022-07-10 5:34 ` Eli Zaretskii
2022-07-10 6:42 ` Visuwesh
2022-07-10 7:32 ` Visuwesh
2022-07-14 6:34 ` Eli Zaretskii
2022-07-14 7:11 ` Visuwesh
2022-07-02 12:15 ` Visuwesh
2022-07-03 3:57 ` Visuwesh
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=83o7y8c983.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56323@debbugs.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).