All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] UTF-8 input: composing non-latin1 characters, and	copy-paste
Date: Mon, 07 Aug 2006 18:43:06 +0600	[thread overview]
Message-ID: <44D7355A.6020006@ums.usu.ru> (raw)
In-Reply-To: <1154953118.25998.31.camel@localhost.localdomain>

Alan Cox wrote:

> Basically I'd rather see us:
> - Expand the kbd code to support the full set of behaviour (within
> reason). It looks like the old behaviour can be expressed by keeping the
> old format and allowing a new format (or mapping the old to the new when
> the ioctl loads it)
> - Expand the kbd code to allow caps/shift mapping by loaded table
> - Store the true symbol not the glyph so we can cut/paste right
> - Do the render mapping of symbols when needed when we actually render
> 
> That also means we get the right results if you move a live console from
> text mode to graphical mode, or load different fonts and refresh.

Indeed. But I am not the one who originally wrote the patch. I only 
fixed a null-pointer dereference in the original patch, updated for a 
new kernel version, and resubmitted. For me, to do what you suggest, 
requires better understanding of the existing code. I will try, though, 
when I get better time.

-- 
Alexander E. Patrakov

  reply	other threads:[~2006-08-07 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 10:55 [PATCH] UTF-8 input: composing non-latin1 characters, and copy-paste Alexander E. Patrakov
2006-08-07 12:18 ` Alan Cox
2006-08-07 12:43   ` Alexander E. Patrakov [this message]
2006-08-07 18:06   ` Jan Engelhardt

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=44D7355A.6020006@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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 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.