From: David De La Harpe Golden <david@harpegolden.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: How to recognize keyboard insertion?
Date: Sun, 01 Nov 2009 05:24:44 +0000 [thread overview]
Message-ID: <4AED1B9C.5070106@harpegolden.net> (raw)
In-Reply-To: <83k4yadi4f.fsf@gnu.org>
Eli Zaretskii wrote:
> OK, but knowing whether to mirror or not requires information about
> whether a given keyboard already mirrors characters. Can this be
> found somewhere, or queried at run time?
[Only if you want to do it automatically, if it was a user preference
the user would just be setting ltr and rtl current input methods as
desired? Or maybe it would be more intuitive to use just one input
method, e.g. hebrew-parenjuggle, expanding the input method layer to
support rtl/ltr context sensitive definitions for individual rules]
It is possible to find out if the current os keyboard layout is us or
hebrew or whatever which could be coupled with prior information that it
is standard for certain layouts to mirror. I don't know exhaustively
which ones do, though a lot could probably be extracted by inspection of
the xkb database.
If OTOH you wanted to find out whether the code a keypress returns under
the current os layout actually corresponds to the glyph printed on the
keyboard, you can't really - Only the user knows that at present as
current keyboards don't really inform the computer what glyphs they have
physically printed on them AFAIK (though it would certainly be
technically feasible for a keyboard to e.g. say "Hi, I am physically a
standard british qwerty 105 key keyboard" to a computer with some
well-defined wire protocol, I don't think typical PC ones do).
next prev parent reply other threads:[~2009-11-01 5:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 15:57 How to recognize keyboard insertion? Eli Zaretskii
2009-10-31 16:58 ` David De La Harpe Golden
2009-10-31 17:20 ` Eli Zaretskii
2009-10-31 17:37 ` David De La Harpe Golden
2009-10-31 17:43 ` David De La Harpe Golden
2009-10-31 18:15 ` Eli Zaretskii
2009-10-31 19:26 ` David De La Harpe Golden
2009-10-31 20:01 ` Eli Zaretskii
2009-10-31 20:42 ` David De La Harpe Golden
2009-10-31 21:23 ` Eli Zaretskii
2009-10-31 21:49 ` David De La Harpe Golden
2009-11-01 3:44 ` Eli Zaretskii
2009-11-01 5:24 ` David De La Harpe Golden [this message]
2009-11-01 19:59 ` Eli Zaretskii
2009-11-01 20:19 ` David De La Harpe Golden
2009-11-01 3:40 ` Stephen J. Turnbull
2009-11-01 5:46 ` David De La Harpe Golden
2009-11-01 5:44 ` tomas
2009-11-01 18:48 ` Eli Zaretskii
2009-11-01 20:09 ` David De La Harpe Golden
2009-11-02 5:03 ` tomas
2009-11-01 1:30 ` Jason Rumney
2009-11-01 4:02 ` Eli Zaretskii
2009-11-01 5:25 ` Stephen J. Turnbull
2009-11-01 13:59 ` David De La Harpe Golden
2009-11-01 19:57 ` Eli Zaretskii
[not found] ` <837huac8gg.fsf@gnu.org>
2009-11-02 14:49 ` Ehud Karni
2009-11-02 19:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AED1B9C.5070106@harpegolden.net \
--to=david@harpegolden.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.