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: arunisaac@systemreboot.net, 58070@debbugs.gnu.org
Subject: bug#58070: [PATCH] Add tamil99 input method
Date: Sun, 25 Sep 2022 17:23:46 +0300	[thread overview]
Message-ID: <83y1u7leh9.fsf@gnu.org> (raw)
In-Reply-To: <87leq7r163.fsf@gmail.com> (message from Visuwesh on Sun, 25 Sep 2022 19:44:44 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: arunisaac@systemreboot.net,  58070@debbugs.gnu.org
> Date: Sun, 25 Sep 2022 19:44:44 +0530
> 
> [ஞாயிறு செப்டம்பர் 25, 2022] Eli Zaretskii wrote:
> 
> >> AFAIK, MS Windows' tamil99 keyboard layout behaves like mine, whereas
> >> the ibus layout behaves like your implementation.  If you are a heavy
> >> user of this layout, can you try out the attached?
> >
> > Please note that we could have support for both layouts, there's no
> > particular reason we should have only one.
> 
> Yes of course but I'm afraid that it will create unneeded confusion,
> since the differences are quite subtle.

Why do you think it will confuse users to have two input methods, each
one for one of the layouts?  If the supported layout is clearly stated
in the documentation (or even in the name of the IM), why would it
confuse?

Please note that we already have several examples where different
input methods for the same language are offered, one each for every
keyboard layout we think users could find useful.  Is Tamil different
in some way?

> So I would prefer the layout which is familiar to most users to get
> in core.

If one of the layouts comes from Windows, the other from Unix, we are
likely to have two large groups of users, each one of which is
familiar with a different layout.  Why not offer them both what they
are familiar with?





  reply	other threads:[~2022-09-25 14:23 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 10:00 bug#58070: [PATCH 0/1] Add tamil99 input method Arun Isaac
2022-09-25 10:02 ` bug#58070: [PATCH] " Arun Isaac
2022-09-25 11:38   ` Visuwesh
2022-09-25 13:59     ` Eli Zaretskii
2022-09-25 14:14       ` Visuwesh
2022-09-25 14:23         ` Eli Zaretskii [this message]
2022-09-25 14:38           ` Visuwesh
2022-09-25 15:55             ` Eli Zaretskii
2022-09-26 20:59               ` Arun Isaac
2022-09-27  6:25                 ` Eli Zaretskii
2022-09-27 20:34                   ` Arun Isaac
2022-09-26 20:55     ` Arun Isaac
2022-09-27  1:49       ` Visuwesh
2022-09-27  2:29         ` Visuwesh
2022-09-27  6:37         ` Eli Zaretskii
2022-09-27  7:34           ` Visuwesh
2022-09-27  7:53             ` Eli Zaretskii
2022-09-27  9:24               ` Robert Pluim
2022-09-27  9:40                 ` Eli Zaretskii
2022-09-27 10:11               ` Visuwesh
2022-09-27 20:32         ` Arun Isaac
2022-09-27  6:23       ` Eli Zaretskii
2022-09-27  7:52         ` Visuwesh
2022-09-27  8:03           ` Eli Zaretskii
2022-09-27 10:15             ` Visuwesh
2022-10-12  8:40             ` Arun Isaac
2022-10-12 14:00               ` Eli Zaretskii
2022-10-15  8:23                 ` Arun Isaac
2022-09-27 20:19           ` Arun Isaac
2022-09-27 20:26         ` Arun Isaac
2022-09-28  2:30           ` Eli Zaretskii
2022-09-25 10:13 ` bug#58070: [PATCH 0/1] " Eli Zaretskii
2022-09-25 11:16   ` Arun Isaac
2022-10-12  8:41     ` Arun Isaac
2022-10-12 13:55       ` Eli Zaretskii
2022-10-15  8:34         ` Arun Isaac
2022-10-15  9:16           ` bug#58070: [PATCH v2] " Arun Isaac
2022-10-15 14:42           ` bug#58070: [PATCH 0/1] " Visuwesh
2022-10-18  7:11             ` Arun Isaac
2022-10-18 18:00               ` bug#58070: [PATCH v3] " Arun Isaac
2022-10-19 11: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=83y1u7leh9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58070@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    --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).