From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] Re: rotation.
Date: Thu, 9 Jan 2003 22:35:58 +0000 (UTC) [thread overview]
Message-ID: <avktge$22o$1@penguin.transmeta.com> (raw)
In-Reply-To: 1042153388.28469.17.camel@irongate.swansea.linux.org.uk
In article <1042153388.28469.17.camel@irongate.swansea.linux.org.uk>,
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
>Note btw that the support ends rather abruptly on the console input side.
>There is no support for 3 or 4 byte utf8 input sequences and the delete
>key code in the kernel has no understanding of or support for UTF8
>deletion behaviour
UTF8 delete behaviour should be pretty trivial to add. It's liketly to
be more involved than simply adding a
/* multi-char UTF8 thing? Continue until we hit the first one */
if (tty->utf8 && (c & 0x80) && !(c & 0x40))
continue;
to the loop in n_tty.c: eraser(), but it might not be _much_ more than
that.
Linus
next prev parent reply other threads:[~2003-01-09 22:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 22:44 rotation James Simmons
2003-01-08 10:24 ` rotation Geert Uytterhoeven
2003-01-08 10:48 ` [Linux-fbdev-devel] rotation Sven Luther
2003-01-08 11:25 ` Måns Rullgård
2003-01-08 12:05 ` John Bradford
2003-01-08 12:55 ` Sven Luther
2003-01-09 10:00 ` Helge Hafting
2003-01-09 19:59 ` James Simmons
2003-01-09 23:03 ` Alan Cox
2003-01-09 22:35 ` Linus Torvalds [this message]
2003-01-10 3:45 ` Alan Cox
2003-01-09 19:45 ` James Simmons
2003-01-09 19:44 ` rotation James Simmons
2003-01-08 16:56 ` [Linux-fbdev-devel] rotation Antonino Daplas
2003-01-09 19:54 ` James Simmons
2003-01-10 10:26 ` Antonino Daplas
2003-01-10 19:42 ` James Simmons
2003-01-10 21:10 ` Kernel 2.5.55 failed to boot with ACPI support Ole J. Hagen
2003-01-11 5:13 ` [Linux-fbdev-devel] rotation Antonino Daplas
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='avktge$22o$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--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