From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Cc: DervishD <lkml@dervishd.net>
Subject: Re: Kernel utf-8 handling
Date: Fri, 1 Jun 2007 23:17:00 +0100 [thread overview]
Message-ID: <20070601221700.GA15242@deepthought> (raw)
In-Reply-To: <20070601142058.GA2587@DervishD>
On Fri, Jun 01, 2007 at 04:20:58PM +0200, DervishD wrote:
> Hi all :)
>
> I have a do-it-yourself Linux box, and I'm planning to move to UTF8
> (currently I'm using es_ES locale, with latin1 encoding). One of my main
> concerns (apart from programs with little or no utf8 support, which I
> will have to suffer) is kernel handling, because I only use the console;
> I only use X and a terminal emulator if I can't avoid it.
>
[...]
>
> Will the console work as it works now if I can live with latin1
> accented characters only? Is there any terminal emulator *for the
> console*, not for X, that handles utf8? Will I be sentenced to X to be
> able to use my computer with utf8?
>
Sure, the console will work (don't know about a console terminal
emulator). I'm not very keen on compose keys - I find dead
diacriticals (like in X) are usually easier to enter, and I've got
all the dead latin1 accents working on my uk keymap. Other
diacriticals for normally-latin1 keymaps are a different matter
(e.g. caron, ogonek, dot above) - they could be mapped for a
specific letter on a specific key (e.g. AltGr z for ż ; z with dot
above) but the diacritical modifiers can't be mapped for non latin1,
at least in kbd-1.12. You can also alter the keymap to allow you do
ISO 14755 input (ctrl+shift+hex_digits) - useful for occasional
characters, if they are in your font and you can remember their
value.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2007-06-01 22:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 14:20 Kernel utf-8 handling DervishD
2007-06-01 14:30 ` CaT
2007-06-01 14:39 ` DervishD
2007-06-01 15:51 ` Éric Piel
2007-06-02 7:35 ` DervishD
2007-06-01 16:28 ` Alexander E. Patrakov
2007-06-01 16:41 ` Alexander E. Patrakov
2007-06-02 7:45 ` DervishD
2007-06-02 10:52 ` Jan Engelhardt
2007-06-02 7:43 ` DervishD
2007-06-01 19:21 ` Jan Engelhardt
2007-06-01 22:24 ` H. Peter Anvin
2007-06-02 7:58 ` DervishD
2007-06-02 10:51 ` Jan Engelhardt
2007-06-02 19:53 ` DervishD
2007-06-02 7:53 ` DervishD
2007-06-01 20:49 ` [PATCH] " Jan Engelhardt
2007-06-01 22:17 ` Ken Moffat [this message]
2007-06-02 7:51 ` DervishD
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=20070601221700.GA15242@deepthought \
--to=zarniwhoop@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dervishd.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.