From: Andrew Morton <akpm@linux-foundation.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: linux-kernel@vger.kernel.org,
linuxconsole-dev@lists.sourceforge.net, akpm@google.com
Subject: Re: [PATCH] unicode diacritics support
Date: Thu, 9 Aug 2007 12:46:42 -0700 [thread overview]
Message-ID: <20070809124642.fbbd3e68.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070808081010.GA3292@implementation.labri.fr>
On Wed, 8 Aug 2007 10:10:10 +0200
Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> There have been issues with non-latin1 diacritics and unicode.
> http://bugzilla.kernel.org/show_bug.cgi?id=7746
>
> Git 759448f459234bfcf34b82471f0dba77a9aca498 `Kernel utf-8 handling'
> partly resolved it by adding conversion between diacritics and
> unicode. The patch below goes further by just turning diacritics into
> unicode, hence providing better future support. The kbd support can be
> fetched from
> http://bugzilla.kernel.org/attachment.cgi?id=12313
>
> This was tested in all of latin1, latin9, latin2 and unicode with french
> and czech dead keys.
>
> --
>
> Turn the kernel accent_table into unicode, and extend ioctls KDGKBDIACR
> and KDSKBDIACR into their equivalents KDGKBDIACRUC and KDSKBDIACR.
>
> New function int conv_uni_to_8bit(u32 uni) for converting unicode into 8bit
> _input_. No, we don't want to store the translation, as it is potentially
> sparse and large.
This changes the kernel ABI a bit. The KDGKBDIACR ioctl (and friends)
now return different data. What are the implications of this?
next prev parent reply other threads:[~2007-08-09 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 8:10 Samuel Thibault
2007-08-09 19:46 ` Andrew Morton [this message]
2007-08-09 19:53 ` Samuel Thibault
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=20070809124642.fbbd3e68.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akpm@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
--cc=samuel.thibault@ens-lyon.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®