From: "David Gómez" <david@pleyades.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Simos Xenitellis <simos74@gmx.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Improved console UTF-8 support for the Linux kernel?
Date: Sun, 12 Dec 2004 01:38:57 +0100 [thread overview]
Message-ID: <20041212003857.GA14844@fargo> (raw)
In-Reply-To: <Pine.LNX.4.61.0412120058230.15129@yvahk01.tjqt.qr>
Hi Jan ;),
> >I am not sure how you wrote the above characters. According to UTF-8,
> >characters with codepoints above 0x79 require two bytes so that to be
> >valid. When you compose "ö" (you press something like ";", then "o") in
> >the console?
>
> ö is a "native key" on my keyboard, i.e. i do not need to play with compose to
> generate ö.
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 :-/
regards,
--
David Gómez Jabber ID: davidge@jabber.org
next prev parent reply other threads:[~2004-12-12 0:39 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
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 [this message]
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=20041212003857.GA14844@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.