unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15800@debbugs.gnu.org
Subject: bug#15800: 24.3.50; hebrew: describe-input-method, case sensitive or not
Date: Tue, 05 Nov 2013 09:29:11 +0530	[thread overview]
Message-ID: <87k3gn5wj4.fsf@gmail.com> (raw)
In-Reply-To: <83li1483j5.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 Nov 2013 19:45:02 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> I wonder what can we say in the introductory text before the layout,
> to make this point clear.

Sorry, I won't make any textual suggestions.

There is a one-to-one correspondence between the standard layout and the
layout that is displayed.  The problem is that the standard layout is
displayed elsewhere.  (Do you really want me to split the window and
have standard layout on top buffer and hebrew layout on the bottom
buffer and figure out what comes first, uppercase or lowercase.)

Displaying standard layout and virtual layout together (preferably
side-by-side will help.)

----------------------------------------------------------------

ALSO, A simple example saying 'typing s gets you this' and 'typing S
gets you that will help'.

----------------------------------------------------------------

OR

You can simply do away with displaying the keyboard(s). Instead, give a
one-to-one map between the input char and the output char.

For example, see quail-help with input method set to tamil-itrans.







  parent reply	other threads:[~2013-11-05  3:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 15:03 bug#15800: 24.3.50; hebrew: describe-input-method, case sensitive or not Jambunathan K
2013-11-04 16:25 ` Eli Zaretskii
2013-11-04 16:32   ` Jambunathan K
2013-11-04 17:01     ` Eli Zaretskii
2013-11-04 17:09       ` Jambunathan K
2013-11-04 17:45         ` Eli Zaretskii
2013-11-04 18:05           ` Eli Zaretskii
2013-11-04 18:35           ` Jambunathan K
2013-11-04 20:05             ` Eli Zaretskii
2013-11-05  3:59           ` Jambunathan K [this message]
2013-11-05  4:02             ` Jambunathan K
2013-11-05 16:38             ` Eli Zaretskii
2013-11-05 17:29               ` Jambunathan K
2013-11-05 13:00         ` 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=87k3gn5wj4.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=15800@debbugs.gnu.org \
    --cc=eliz@gnu.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).