From: "David Gómez" <david@pleyades.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Simos Xenitellis <simos74@gmx.net>, linux-kernel@vger.kernel.org
Subject: Re: Improved console UTF-8 support for the Linux kernel?
Date: Sat, 11 Dec 2004 23:01:38 +0100 [thread overview]
Message-ID: <20041211220138.GE14168@fargo> (raw)
In-Reply-To: <Pine.LNX.4.53.0412112234550.2492@yvahk01.tjqt.qr>
Hi Jan ;),
On Dec 11 at 10:39:55, Jan Engelhardt wrote:
> Yes it does generate 0xC3B6 (otherwise it would show up as garbage, because it
> would not be utf8-compliant if it only output 0xF6)
>
> >I'm using kernel 2.6.9 + Chris patch
>
> I am using SUSE's KOTD 20041202 (2.6.8 + 2.6.9-rc2)
Maybe the patch or a fix has already been included in rc2/rc3, or in
SUSE's version :??
> >method. I've used it with anthy, just have to check it with skk.
>
> Have not seen it. What is it? Some sort of xterm?
Just an input system. To be able to write Japanese all over the place ;))
regards,
--
David Gómez Jabber ID: davidge@jabber.org
next prev parent reply other threads:[~2004-12-11 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 17:06 Improved console UTF-8 support for the Linux kernel? Simos Xenitellis
2004-12-11 17:30 ` David Gómez
2004-12-11 19:07 ` Jan Engelhardt
2004-12-11 21:25 ` David Gómez
2004-12-11 21:39 ` Jan Engelhardt
2004-12-11 22:01 ` David Gómez [this message]
2004-12-11 22:26 ` Gene Heskett
[not found] ` <1102803807.3183.59.camel@kl>
2004-12-12 0:05 ` Jan Engelhardt
2004-12-12 0:38 ` David Gómez
2004-12-12 22:08 ` Simos Xenitellis
2004-12-12 22:14 ` Jan Engelhardt
2004-12-12 23:06 ` David Gómez
2004-12-12 23:52 ` Andries Brouwer
2004-12-12 15:44 ` Lehmann
-- strict thread matches above, loose matches on Subject: below --
2004-12-12 14:02 Simos Xenitellis
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=20041211220138.GE14168@fargo \
--to=david@pleyades.net \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=simos74@gmx.net \
/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