unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 9336@debbugs.gnu.org
Subject: bug#9336: 24.0.50; No way to input character #xbb4 using ta-itrans
Date: Thu, 22 Sep 2011 11:42:21 +0900	[thread overview]
Message-ID: <tl7ty85b8mq.fsf@m17n.org> (raw)
In-Reply-To: <814o068rbu.fsf@gmail.com> (message from Jambunathan K on Wed, 21 Sep 2011 09:44:29 +0530)

In article <814o068rbu.fsf@gmail.com>, Jambunathan K <kjambunathan@gmail.com> writes:

>>> (Rationale: This is how it's usually mapped by a layman even outside of
>>> ta-itrans)
> >
> > "zha" would be more appropriate.  Just to pick two contemporary names
> > that have ழ in them, we have Azhagiri and Kanimozhi.

> (For Kenichi's benefit) The two things that you have cited above are
> Tamil people names.

Thank you for the info. 

> Are you making the suggestion - "zha" - based on an actual itrans
> implementation? Within Emacs, if I type - `zha' - I get `ழ்ஹ' and mapping
> `ha' to `ஹ' seems very reasonable to me.

> IMO, there seems to be some de-facto or normative standard on how
> english sequences are mapped to tamil alphabets (or any given language?)
> via itrans. In that case, there is nothing much Emacs can do but follow
> the crowd.

> I am a layman user, I don't have any prior experience with other
> ta-itrans implementations and Kenichi is the expert here.

All I know about itrans is that it's originally a method for
roman transliteration of Indic scripts, not an input method.
So, using itrans as an input method may reveal various
shortages/conflicts of the original itrans definition, and
thus we must extend/modify the mapping between keys and
chars.  But, I don't know what kind of defact standard there
are.

For the above case, which is more convenient?
(1) "zha" -> "ழ்ஹ" and "za" -> "ழ"
(2) "zha" -> "ழ", "za" -> "zஅ", and "zhha" -> "ழ்ஹ".

---
Kenichi Handa
handa@m17n.org





  reply	other threads:[~2011-09-22  2:42 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
2011-09-21  3:45       ` Vijay Lakshminarayanan
2011-09-21  4:14         ` Jambunathan K
2011-09-22  2:42           ` Kenichi Handa [this message]
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=tl7ty85b8mq.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=9336@debbugs.gnu.org \
    --cc=kjambunathan@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).