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-done@debbugs.gnu.org, rameshnedunchezian@outlook.com
Subject: bug#50143: 28.0.50; Various issues with `tamil-itrans' input method
Date: Sun, 13 Mar 2022 10:23:33 +0200	[thread overview]
Message-ID: <83wngyl0qi.fsf@gnu.org> (raw)
In-Reply-To: <87cziqgw4b.fsf@gmail.com> (message from Visuwesh on Sun, 13 Mar 2022 12:46:52 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: 50143@debbugs.gnu.org,  rameshnedunchezian@outlook.com
> Date: Sun, 13 Mar 2022 12:46:52 +0530
> 
> >>     1. There's still a problem with tamil-itrans docstring.  It
> >>        currently leads the user into thinking that they can input the
> >>        Tamil digits.  The problem is that I am not sure how I can split
> >>        `quail-tamil-itrans-various-signs-and-digits-table' into two
> >>        cleanly.  Ideas are welcome.
> >
> > I'd split into two parts the code that computes
> > quail-tamil-itrans-various-signs-and-digits-table, such that the Tamil
> > digits are in a separate part.  Then change the doc strings of the two
> > input methods so that the digits part is only included in the
> > documentation of the input method that supports their insertion.
> >
> 
> How does the updated patch look?

LGTM, installed.

> >>    2. The problem with the include variable syntax is because `quail-help'
> >>       (which is used eventually by `describe-input-method') calls
> >>       `substitute-command-keys' on the docstring so to get the intended
> >>       behaviour, one has to write \\=\\<VAR> not \\<VAR>.  The logic,
> >>       otherwise, is fine.  Maybe this needs to be documented?
> >
> > Yes, please.
> >
> 
> I tried to fix this, please see attached patch,

Thanks, installed.

> > Btw, the patch is already close to the limit of what we can accept
> > without copyright assignment, so would you like to start your legal
> > paperwork rolling at this time, so that we could in the future accept
> > more contributions from you?  If yes, I will send you the form to fill
> > and the instructions to go with that.
> >
> 
> BTW, I sent the mail to assign@gnu.org on 23rd Feb, and haven't heard
> from them yet.

Please send a reminder to them and CC me.  Thanks.





  reply	other threads:[~2022-03-13  8:23 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
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 [this message]
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=83wngyl0qi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50143-done@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).