mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guest section DW <dwguest@win.tue.nl>
To: Radovan Garabik <garabik@melkor.dnp.fmph.uniba.sk>,
	linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] dead keys in unicode console mode
Date: Tue, 9 Oct 2001 04:16:18 +0200	[thread overview]
Message-ID: <20011009041618.A6135@win.tue.nl> (raw)
In-Reply-To: <20011008215313.A11879@melkor.dnp.fmph.uniba.sk>
In-Reply-To: <20011008215313.A11879@melkor.dnp.fmph.uniba.sk>; from Radovan Garabik on Mon, Oct 08, 2001 at 09:53:13PM +0200

On Mon, Oct 08, 2001 at 09:53:13PM +0200, Radovan Garabik wrote:
> FWIW, this little patch makes it possible to
> use dead keys in unicode console mode.
> It is against 2.4.10, but should apply cleanly in
> broader range of kernel versions.

>  struct kbdiacr {
> -        unsigned char diacr, base, result;
> +        unsigned char diacr, base;
> +        unsigned short int result; /* holds UCS2 value */
>  };

And now all existing binaries that use the KDGKBDIACR ioctl
dump core? And all existing binaries that use the KDSKBDIACR
ioctl do very strange things?

If you want to do something like this, a new ioctl and a new
structure are necessary. If you design something new, keep
examples like Vietnamese in mind (with several accents on
one symbol). We do support that now in the 8-bit world,
but complete support of the 16-bit world still requires
some work. (And in the meantime Unicode has already gone beyond.)

  reply	other threads:[~2001-10-09  2:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-08 19:53 Radovan Garabik
2001-10-09  2:16 ` Guest section DW [this message]
2001-10-09  2:25   ` H. Peter Anvin
2001-10-09  7:28   ` Radovan Garabik
2001-10-10 17:19     ` Pavel Machek
2001-10-16  8:03       ` Radovan Garabik

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=20011009041618.A6135@win.tue.nl \
    --to=dwguest@win.tue.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=garabik@melkor.dnp.fmph.uniba.sk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®