From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262165AbULLXHk (ORCPT ); Sun, 12 Dec 2004 18:07:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262168AbULLXHj (ORCPT ); Sun, 12 Dec 2004 18:07:39 -0500 Received: from 90.Red-213-97-199.pooles.rima-tde.net ([213.97.199.90]:48815 "HELO fargo") by vger.kernel.org with SMTP id S262165AbULLXHd (ORCPT ); Sun, 12 Dec 2004 18:07:33 -0500 Date: Mon, 13 Dec 2004 00:06:57 +0100 From: David =?iso-8859-15?Q?G=F3mez?= To: Simos Xenitellis Cc: Jan Engelhardt , Linux Kernel Mailing List Subject: Re: Improved console UTF-8 support for the Linux kernel? Message-ID: <20041212230657.GA18397@fargo> Mail-Followup-To: Simos Xenitellis , Jan Engelhardt , Linux Kernel Mailing List References: <1102784797.4410.8.camel@kl> <20041211173032.GA13208@fargo> <1102803807.3183.59.camel@kl> <20041212003857.GA14844@fargo> <1102889302.3195.10.camel@kl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1102889302.3195.10.camel@kl> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi Simon ;), On Dec 12 at 10:08:22, Simos Xenitellis wrote: > > Aaahh ;), you've should said that before. The whole problem with the > > kernel is with the compose tables. If you have a native key for "ö" in > > your keyboard you'll not have problems. I can type for example a 'n > > with tilde' in my keyboard because is too is a native key, but for > > accentuated characters, for utf-8 output is neccesary to apply the patch :-/ > > And that's the whole issue. > > As soon as the kernel is in Unicode mode for the console, currently > there is no way to input accented characters through a dead key > (composed). True. > Some years back when 8-bit encodings where used there was no problem, > however now all distros are broken with regards to this. I guess that some distros use their own patches, like it seems with SuSE, but it's something that it's broken in the linux console and should be fixed. > I do not know what is the next step to consider adding the patch. Submitting the patch to lkml to discuss about its possible inclusion would be a good start. I don't know who's the console maintainer, Vojtech Pavlik perhaps? Regards, -- David Gómez Jabber ID: davidge@jabber.org