unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 50143@debbugs.gnu.org, rameshnedunchezian@outlook.com
Subject: bug#50143: 28.0.50; Various issues with `tamil-itrans' input method
Date: Wed, 16 Feb 2022 19:36:36 +0200	[thread overview]
Message-ID: <83wnhu1zob.fsf@gnu.org> (raw)
In-Reply-To: <874k509w4k.fsf@gmail.com> (message from Visuwesh on Tue, 15 Feb 2022 17:31:31 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>,
>   50143@debbugs.gnu.org
> Date: Tue, 15 Feb 2022 17:31:31 +0530
> 
> >> 3. `indian-make-hash` ALWAYS installs translation for decimal digits
> >>    0-9.  Tamil decimal digits are NOT used at all i.e., it is not even
> >>    taught in Schools in the state of TamilNadu, India.  So, I wanted a
> >>    way NOT to insall the translation for digits.  I suggest one of the
> >>    following:
> >> 
> >>    - Change signature of `(indian-make-hash TABLE TRANS-TABLE)' to
> >>      `(indian-make-hash TABLE TRANS-TABLE &optional
> >>      DONT-INSTALL-NATIVE-DIGITS)' or some such thing.
> >
> > This change of the API is acceptable, so please propose a patch along
> > these lines.
> >
> 
> I wanted to send a patch so I took a quick look at ind-util.el, and ISTM
> that the hashtable `indian-tml-itrans-v5-hash' is calculated just once?
> Unfortunately, I don't understand the dances in ind-util.el,
> lisp/leim/indian.el, etc. so I'm afraid I cannot be of any help here.
> 
> [ It should be a simple change if we don't make it a defcustom AFAIU.  ]
> 
> >>      `indian-make-hash' is used by many indic scripts, so I am not
> >>      sure if other indian language users would have a need for
> >>      inputting native decimal digits.  I--as a representative of Tamil
> >>      speakers--can say that we don't need that ON by default.
> >
> > We can use this for Tamil only for now, and wait for users of other
> > languages to chime in.
> >
> > Thanks.
> 
> As a native Tamil speaker, I can attest that contemporary text uses the
> Arabic numerals (in fact, Tamil digits are mentioned as a matter of fact
> in schools).  I'm not sure about the situation in Sri Lanka, tho.

It sounds like a better way forward would be to define a separate
input method, so that the existing input method is preserved and can
be used if someone wants the current transliterations.

So my suggestions would be:

 1. For your items 1 and 3, just copy indian-tml-base-table to a new
    variable, modify it to include the two missing characters and
    replace the digits with nil, add a new variable similar to
    indian-tml-itrans-v5-hash, and compute its value like we do with
    indian-tml-itrans-v5-hash, but using the new table instead of
    indian-tml-base-table.  Then make a new input method, called, say,
    tamil-itrans-alt, which would use the new hash variable instead of
    indian-tml-itrans-v5-hash.  Submit these changes as patches to
    lisp/language/ind-util.el and lisp/leim/quail/indian.el.

 2. For your item 2, submit a patch that fixes the docstring of the
    relevant input methods.

Would that work for you?  Can you prepare such patches?





  reply	other threads:[~2022-02-16 17:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-21  9:25 bug#50143: 28.0.50; Various issues with `tamil-itrans' input method Ramesh Nedunchezian
2021-08-22  7:28 ` Eli Zaretskii
2022-02-15 12:01   ` Visuwesh
2022-02-16 17:36     ` Eli Zaretskii [this message]
2022-02-17  2:14       ` Visuwesh
2022-02-17  6:33         ` Eli Zaretskii
2022-02-17 10:53       ` Visuwesh
2022-02-17 17:30         ` Eli Zaretskii
2022-02-18  1:01           ` Visuwesh
2022-02-18  7:58             ` Eli Zaretskii
2022-03-13  5:51           ` Visuwesh
2022-03-13  5:59             ` Visuwesh
2022-03-13  6:35               ` Eli Zaretskii
2022-03-13  7:16                 ` Visuwesh
2022-03-13  8:23                   ` Eli Zaretskii
2022-03-13  9:01                     ` Visuwesh
2022-03-13  9:41                       ` Eli Zaretskii

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=83wnhu1zob.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50143@debbugs.gnu.org \
    --cc=rameshnedunchezian@outlook.com \
    --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).