unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Amit Ramon <amit.ramon@riseup.net>
Cc: emacs-devel@gnu.org
Subject: Re: Issues with quail.el
Date: Tue, 08 May 2018 20:28:06 +0300	[thread overview]
Message-ID: <83o9hqoy55.fsf@gnu.org> (raw)
In-Reply-To: <20180508084140.ao5rwz7lupl3pyly@isis.luna> (message from Amit Ramon on Tue, 8 May 2018 11:41:40 +0300)

> Date: Tue, 8 May 2018 11:41:40 +0300
> From: Amit Ramon <amit.ramon@riseup.net>
> 
> Eli Zaretskii <eliz@gnu.org> [2018-05-07 22:33 +0300]:
> 
> >
> >I'm no expert on this, but does the fact that Dvorak keyboards need
> >special input methods tell anything useful for your use case?
> 
> Perhaps I wasn't clear enough. I've been using Dvorak keyboard layout
> (defined at X level, physical keyboard is standard one) with Hebrew
> input method for quite many years, and as for typing, i.e. inputting
> Hebrew characters, everything works just fine. Dvorak keyboard doesn't
> need special input method - AFAIK quail is designed to work with any
> keyboard layout - you just have to tell quail about it.
> 
> The problems I'm talking about are "second order" - they are related to
> functions that display information about input methods and keyboard
> layouts.

My point was that maybe the "second-order" problems you bumped into do
need something special like Dvorak input methods do.

And we do have special input methods for Dvorak keyboard layouts,
AFAIK: e.g., see programmer-dvorak and English-dvorak.

> I spent quiet a lot of time trying to resolve the exact problem and
> how to fix it, but I have to admit that quail is quiet complex so I'd
> appreciate some directions from people who understand it better than
> me.

I'm afraid all the experts on this matter are quite silent for several
years.  But maybe someone will chime in...




  reply	other threads:[~2018-05-08 17:28 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 [this message]
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
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

  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=83o9hqoy55.fsf@gnu.org \
    --to=eliz@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 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).