From: Eli Zaretskii <eliz@gnu.org>
To: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Not able to display \u110BD and \u110CD in Emacs
Date: Sat, 30 Apr 2022 10:00:42 +0300 [thread overview]
Message-ID: <834k2b9ht1.fsf@gnu.org> (raw)
In-Reply-To: <CAOR1sLyporyAcdz6B5pYW9Y-wPwESuF4pBAruqUeJExApsFatQ@mail.gmail.com> (message from समीर सिंह Sameer Singh on Sat, 30 Apr 2022 11:40:03 +0530)
> From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> Date: Sat, 30 Apr 2022 11:40:03 +0530
> Cc: emacs-devel@gnu.org
>
> btw, is the way how I have written the composition table correct? I have copied it from the Brahmi
> composition one, or is it more apporpriate to do it in the way of the devanagari, bengali, malayalam ones?
It doesn't matter. Whatever is more convenient for reading and
understanding the rules is preferable.
> Also I plan to include more writing scripts in emacs, so should I send the patches one by one or in bulk?
Separate patches, please.
Please also include with the patches the relevant additions to the
etc/HELLO file, and also don't forget to make sure
script-representative-chars has representative characters for the
script -- this is important for selecting fonts for those characters.
However, if you intend to submit more patches, I suggest to start your
legal paperwork of assigning the copyright to the FSF, so that we
could accept those future contributions from you. If you agree, I
will send you the form now.
next prev parent reply other threads:[~2022-04-30 7:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 23:17 Not able to display \u110BD and \u110CD in Emacs समीर सिंह Sameer Singh
2022-04-29 5:52 ` Eli Zaretskii
2022-04-29 6:53 ` Eli Zaretskii
2022-04-29 9:45 ` समीर सिंह Sameer Singh
2022-04-29 10:50 ` Eli Zaretskii
2022-04-29 11:17 ` समीर सिंह Sameer Singh
2022-04-29 12:18 ` Eli Zaretskii
2022-04-29 15:26 ` समीर सिंह Sameer Singh
2022-04-29 16:13 ` Eli Zaretskii
2022-04-30 4:52 ` समीर सिंह Sameer Singh
2022-04-30 6:03 ` Eli Zaretskii
2022-04-30 6:10 ` समीर सिंह Sameer Singh
2022-04-30 7:00 ` Eli Zaretskii [this message]
2022-04-30 7:03 ` समीर सिंह Sameer Singh
2022-04-30 7:19 ` Eli Zaretskii
2022-04-30 8:01 ` समीर सिंह Sameer Singh
2022-05-05 15:53 ` Madhu
2022-05-05 16:09 ` समीर सिंह Sameer Singh
2022-05-05 16:43 ` Madhu
2022-05-05 17:06 ` समीर सिंह Sameer Singh
2022-05-05 16:47 ` Eli Zaretskii
2022-05-06 3:59 ` Madhu
2022-05-06 5:56 ` Eli Zaretskii
2022-05-07 7:01 ` Eli Zaretskii
2022-05-07 14:19 ` Madhu
2022-05-07 14:22 ` Eli Zaretskii
2022-05-07 14:29 ` समीर सिंह Sameer Singh
2022-05-07 14:56 ` Eli Zaretskii
2022-05-07 15:47 ` Madhu
2022-05-07 16:01 ` समीर सिंह Sameer Singh
2022-05-07 16:44 ` Madhu
2022-05-07 16:54 ` समीर सिंह Sameer Singh
2022-05-08 17:25 ` Madhu
2022-05-08 17:35 ` Eli Zaretskii
2022-05-08 18:21 ` Madhu
2022-05-08 18:59 ` Eli Zaretskii
2022-05-09 2:06 ` Madhu
2022-05-09 2:39 ` Eli Zaretskii
2022-05-07 14:57 ` Madhu
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=834k2b9ht1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lumarzeli30@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).