public inbox for kbd@lists.linux.dev
 help / color / mirror / Atom feed
From: Michael Schutte <michi@uiae.at>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] [PATCH] Enable UNUMBERs in compose definitions
Date: Thu, 30 Jul 2009 13:39:32 +0200	[thread overview]
Message-ID: <20090730113932.GA22357@amilo.homenet> (raw)
In-Reply-To: <4A7183AE.3000402@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

Hi,

On Thu, Jul 30, 2009 at 03:27:42PM +0400, Alexey Gladkov wrote:
> You added UNUMBER to CCHAR for COMPOSE.
> 
> Can you explain your patch in more detail?

Sure!

Since 18eadfe…, loadkeys supports the composition of two Unicode keysyms
to another Unicode keysym.  Whereas the resulting char could already be
specified as U+…, diacr and base had to be given as 8-bit characters,
which is ugly with today’s Unicode support.  Since it isn’t realistic to
make keymaps capable of UTF-8, I was asked by a Debian developer to at
least make it possible to specify Unicode codepoints.  rvalue is
unsuitable at this point (because it does some trickery with KT_LATIN
vs. KT_LETTER which is not applicable here), I decided to add this to a
new expression just for compose.

-- 
Michael Schutte <michi@uiae.at>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2009-07-30 11:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 11:55 [kbd] [PATCH] Enable UNUMBERs in compose definitions Michael Schutte
2009-07-28 22:41 ` Alexey Gladkov
2009-07-29  7:55   ` Michael Schutte
2009-07-30 11:27     ` Alexey Gladkov
2009-07-30 11:39       ` Michael Schutte [this message]
2009-07-30 12:17         ` Alexey Gladkov
2009-07-30 12:36           ` Michael Schutte
2009-07-30 15:22             ` Alexey Gladkov

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=20090730113932.GA22357@amilo.homenet \
    --to=michi@uiae.at \
    --cc=kbd@lists.altlinux.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox