public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel utf-8 handling
Date: Sat, 2 Jun 2007 09:51:18 +0200	[thread overview]
Message-ID: <20070602075118.GA20406@DervishD> (raw)
In-Reply-To: <20070601221700.GA15242@deepthought>

    Hi Ken :)

 * Ken Moffat <zarniwhoop@ntlworld.com> dixit:
> On Fri, Jun 01, 2007 at 04:20:58PM +0200, DervishD wrote:
> >     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.

    I only use compose keys for a bunch of characters like © (copyright
mark) for example. For any other I use dead diacriticals (for example,
to write the accented chars for my mother tongue).

> 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.

    I have my keymap modified for that, and I use it as a last resort.
If I find myself using AltGr+hex (that's the key combo I use), I usually
put that character in a compose.

    Thanks for the info, I'm very happy to hear that it works :)))

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

      reply	other threads:[~2007-06-02  7:49 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
2007-06-02  7:51   ` DervishD [this message]

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=20070602075118.GA20406@DervishD \
    --to=lkml@dervishd.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zarniwhoop@ntlworld.com \
    /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