From: handa@gnu.org (K. Handa)
To: Amit Ramon <amit.ramon@riseup.net>
Cc: emacs-devel@gnu.org
Subject: Re: Issues with quail.el
Date: Sat, 12 May 2018 21:24:54 +0900 [thread overview]
Message-ID: <87po21f4dl.fsf@gnu.org> (raw)
In-Reply-To: <20180510141234.tpj4vagod6bejmta@isis.luna> (message from Amit Ramon on Thu, 10 May 2018 17:12:34 +0300)
Very sorry for the late response.
In article <20180510141234.tpj4vagod6bejmta@isis.luna>, Amit Ramon <amit.ramon@riseup.net> writes:
> > When I try to recreate what you are showing, I get the following.
> > Does this match?
> >
> > +----------------------------------------------------------------+
> > | 1! | 2" | 3§ | 4$ | 5% | 6& | 7/ | 8( | 9) | 0( | ß? | '` | ;^ |
> > +----------------------------------------------------------------+
> > | qQ | 'W | קE | רR | אT | טZ | וU | ןI | םO | פP | ]} | [{ |
> > +------------------------------------------------------------+
> > | שA | דS | גD | כF | עG | יH | חJ | לK | ךL | ףÖ | ,Ä | ~| |
> > +--------------------------------------------------------------+
> > | >< | זY | סX | בC | הV | נB | מN | צM | ת> | ץ< | ._ |
> > +------------------------------------------------------+
[...]
> This is what it should look like:
> +----------------------------------------------------------------+
> | 1! | 2@ | 3# | 4$ | 5% | 6^ | 7& | 8* | 9) | 0( | -_ | =+ | `~ |
> +----------------------------------------------------------------+
> | /Q | 'W | קE | רR | אT | טY | וU | ןI | םO | פP | ]} | [{ |
> +------------------------------------------------------------+
> | שA | דS | גD | כF | עG | יH | חJ | לK | ךL | ף: | ," | \| |
> +-----------------------------------------------------------+
> | זZ | סX | בC | הV | נB | מN | צM | ת> | ץ< | .? |
> +-------------------------------------------------+
[...]
> Note, for example, the location of the "Y" and "Z", and the two keys
> right of the "L". This layout is the standard for a Hebrew keyboard
> layout (the Israeli standard, at least), and this is what a Hebrew
> writer would expect when Hebrew input method is set. (you can get it
> simply if you don't change your keyboard layout -- assuming it is the
> standard one -- and then set input method to Hebrew, and do C-h I.)
It seems that the difference is at such a key that is different from the
standard layout and that is not mapped to Hebrew. So, I suspect that
the code (in quail-insert-kbd-layout) handling such a key should be
fixed. Could you please try the attached patch?
[...]
> What I get for the second letter (TET, ט) is:
> ט can't be input by the current input method
I confimed this bug, but it seems that fixing take more time. Please wait.
> (add-to-list 'quail-keyboard-layout-alist
> `("dvorak" . ,(concat " "
> " 1!2@3#4$5%6^7&8*9(0)[{]}`~ "
> " '\",<.>pPyYfFgGcCrRlL/?=+ "
> " aAoOeEuUiIdDhHtTnNsS-_\\| "
> " ;:qQjJkKxXbBmMwWvVzZ "
> " ")))
> (quail-set-keyboard-layout "dvorak")
> If you actually evaluate this elisp code, you could call
> "quail-set-keyboard-layout" once with "dvorak" and once with
> "standard" and compare the results of C-h I (and for that you don't
> have to change the actual layout of the keyboard).
> * Emacs has (see quail.el) definitions for sun-type3, atari-german,
> pc102-de, jp106 and pc105-uk keyboard layouts only, but not Dvorak
> (anyone has an idea why? perhaps it is time to add it?)
I agree.
> [2] The definitions for the standard Hebrew input method ("hebrew" and
> "hebrew-new") do not explicitly define the first shift level. Perhap
> the author of it trusted quail to take this from the English standard
> layout (the first shift level is identical, at least most of
> it). However, perhaps it would be safer to completly define the Hebrew
> layout, including the first shift level.
For that, I don't have a strong opinion. But, I think it is not good to
add extra code for hiding a bug of quail.
---
K. Handa
handa@gnu.org
diff --git a/lisp/international/quail.el b/lisp/international/quail.el
index eece836354..a81244a1db 100644
--- a/lisp/international/quail.el
+++ b/lisp/international/quail.el
@@ -815,7 +815,7 @@ quail-insert-kbd-layout
(aref (cdr translation) 0)
" ")))
(setq done-list (cons translation done-list)))
- (setq translation (aref kbd-layout i)))
+ (setq translation ch))
(aset layout i translation))
(setq i (1+ i)))
next prev parent reply other threads:[~2018-05-12 12:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 11:53 Issues with quail.el Amit Ramon
2018-05-07 19:33 ` Eli Zaretskii
2018-05-08 8:41 ` Amit Ramon
2018-05-08 17:28 ` Eli Zaretskii
2018-05-08 19:53 ` Amit Ramon
2018-05-09 3:19 ` Michael Welsh Duggan
2018-05-10 14:12 ` Amit Ramon
2018-05-11 3:18 ` Van L
2018-05-11 16:41 ` Amit Ramon
2018-05-12 4:13 ` Michael Welsh Duggan
2018-05-12 17:12 ` Amit Ramon
2018-05-12 12:24 ` K. Handa [this message]
2018-05-17 12:31 ` K. Handa
2018-05-17 15:41 ` Amit Ramon
2018-05-17 15:44 ` Filipp Gunbin
2018-05-17 18:57 ` Amit Ramon
2018-05-18 14:36 ` K. Handa
2018-05-19 12:01 ` Amit Ramon
2018-05-23 14:27 ` K. Handa
2018-05-27 13:09 ` Amit Ramon
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=87po21f4dl.fsf@gnu.org \
--to=handa@gnu.org \
--cc=amit.ramon@riseup.net \
--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.