unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Questions about Quail
Date: Sun, 17 Jul 2022 12:13:47 +0530	[thread overview]
Message-ID: <87k08ckzmk.fsf@gmail.com> (raw)
In-Reply-To: <87r12kl4km.fsf@gmail.com> (Visuwesh's message of "Sun, 17 Jul 2022 10:26:57 +0530")

[ஞாயிறு ஜூலை 17, 2022] Visuwesh wrote:

>     2. Currently the quail-keyboard-layout-standard resembles the VT100
>        keyboard layout, can we change it to resemble the US Qwerty
>        layout instead?  This is not a problem when writing a new Quail
>        keyboard layout in quail-keyboard-layout-alist but it is a
>        problem when the keyboard layout is printed.

Hmm, maybe it is better to let the sleeping dogs lie and put with the
confusing keyboard representation...  It seems easy to change the
quail-keyboard-layout-standard to a US Qwerty keyboard layout but since
I don't have any of the other keyboards defined in the alist to test, I
don't think I should touch it.

BTW, if you want a print of these keyboard, you can ask xkb:

    % setxkbmap gb -option -geometry 'pc(pc105)' -print |xkbcomp - - |xkbprint -label symbols - pc105-uk.ps
    % setxkbmap de -option -geometry 'pc(pc102)' -print |xkbcomp - - |xkbprint -label symbols - pc102-de.ps

I can send these postscript files if you're interested.



  reply	other threads:[~2022-07-17  6:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17  4:56 Questions about Quail Visuwesh
2022-07-17  6:43 ` Visuwesh [this message]
2022-07-23  4:21 ` James Thomas
2022-07-23  7:31   ` Visuwesh
2022-07-23  7:55     ` James Thomas
2022-07-23  8:21       ` Visuwesh
2022-07-23  8:38         ` Visuwesh
2022-07-23  9:02           ` Visuwesh
2022-07-23 11:38             ` James Thomas
2022-07-23 12:19               ` Visuwesh
2022-07-23 13:29                 ` James Thomas

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=87k08ckzmk.fsf@gmail.com \
    --to=visuweshm@gmail.com \
    --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).