From: Jambunathan K <kjambunathan@gmail.com>
To: Kenichi Handa <handa@m17n.org>
Cc: 9336@debbugs.gnu.org
Subject: bug#9336: 24.0.50; No way to input character #xbb4 using ta-itrans
Date: Tue, 20 Sep 2011 16:21:13 +0530 [thread overview]
Message-ID: <81y5xj4hcu.fsf@gmail.com> (raw)
In-Reply-To: <tl7wrd9oslo.fsf@m17n.org> (Kenichi Handa's message of "Fri, 16 Sep 2011 16:26:43 +0900")
Hello Kenichi,
Kenichi Handa <handa@m17n.org> writes:
> In article <817h5aarsv.fsf@gmail.com>, Jambunathan K <kjambunathan@gmail.com> writes:
>
>> It would be helpful to include the tables in the order given below. It
>> would be highly desirable that they are enumerated NOT in the unicode
>> order but in their natural order (i.e., the order in which we are taught
>> to recite these alphabets in our schools)
>
> Thank you for the detail. I'll work on it.
>> Footnotes:
>> [1] Independent Vowels Table + Aytham (13 items)
> Within 2D table, I think we can show just one key
> sequence. Which is more common/convenient; A or aa, I or ii, ...?
>> 0B85, அ, a
>> 0B86, ஆ, A or aa
>> 0B88, ஈ, I or ii
>> 0B8A, ஊ, U or uu
Please use A, I, U
(Rationale: I am seeing that there is no `oo' but only a `O'. With the
above choice, one can always enter a capitalized vowel and be assured
that the right thing will happen)
>> 0B99, ங, N^a or ~Na
Please use N^a.
(Rationale: Better to start with an regular character than a punctuation
character)
>> 0B9E, ஞ, JNa or ~na
Please use JNa.
(Rationale: Same as before)
>> 0BB5, வ, wa or va
We can use va.
(Rationale: Seems natural)
>> 0BB3, ள, La or lda
We can use La.
(Rationale: The above character doesn't sound like `lda' when spoken)
>> 0BB4, ழ,
>
> It seems that the above character can't be input with
> tamil-itrans. What key is usually used for that character?
The patch that you had sent earlier works. Could you please commit those
changes?
Above character has two bindings - "za" or "Ja".
We can go with "za".
(Rationale: This is how it's usually mapped by a layman even outside of
ta-itrans)
TIA,
Jambunathan K.
next prev parent reply other threads:[~2011-09-20 10:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 16:47 bug#9336: 24.0.50; No way to input character #xbb4 using ta-itrans Jambunathan K
2011-08-23 4:18 ` Kenichi Handa
2011-08-23 7:23 ` Jambunathan K
2011-08-23 7:55 ` Jambunathan K
2011-08-25 4:27 ` Kenichi Handa
2011-09-15 12:55 ` Jambunathan K
2011-09-16 7:26 ` Kenichi Handa
2011-09-20 10:51 ` Jambunathan K [this message]
2011-09-21 3:45 ` Vijay Lakshminarayanan
2011-09-21 4:14 ` Jambunathan K
2011-09-22 2:42 ` Kenichi Handa
2011-09-22 3:27 ` Vijay Lakshminarayanan
2011-09-22 2:23 ` Kenichi Handa
2011-09-23 11:21 ` Jambunathan K
2011-09-23 11:24 ` Jambunathan K
2011-09-26 7:08 ` Kenichi Handa
2011-09-26 13:53 ` Jambunathan K
2011-09-27 4:50 ` Kenichi Handa
2011-09-28 13:00 ` Jambunathan K
2011-09-29 1:46 ` Kenichi Handa
2011-09-29 1:51 ` Kenichi Handa
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=81y5xj4hcu.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=9336@debbugs.gnu.org \
--cc=handa@m17n.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).