All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Linux-kernel <linux-kernel@vger.kernel.org>, lkml@dervishd.net
Subject: Re: Kernel utf-8 handling
Date: Fri, 01 Jun 2007 22:28:24 +0600	[thread overview]
Message-ID: <46604928.4050002@ums.usu.ru> (raw)
In-Reply-To: <20070601142058.GA2587@DervishD>

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.

The switch is possible. You could try the latest development LFS LiveCD 
(http://ums.usu.ru/~patrakov/test/lfslivecd-x86-6.3-pre2-r1897.iso) and see 
if it works for you (be sure to CC: me if you post any feedback). It will 
automatically configure the console using a simple menu-driven interface. 
Some interesting programs to try there: mutt, tin, lynx, finch.

>     This said, I know that the console will give me no problems
> regarding character representantion (heck, I'm pretty sure that I will
> be able to use even the same font I'm using right now in the console if
> I get the proper unicode map), but probably will give me problems when
> *entering* characters. I've read that the kernel handles accented chars,
> and things like 'ñ' (ntilde) because it assumes that any composed
> character (composed using dead keys, for example) is in the latin1
> range. While this is not a perfect behaviour, it will work for me.

Yes.

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

screen, jfbterm, iterm (jfbterm and iterm are not on my CD, but you can 
build them from source there - the filesystem on the CD can be written to). 
Note that jfbterm and iterm expect X fonts (or unifont) to be available, and 
the CD doesn't have these fonts (fully switched to Xft).

-- 
Alexander E. Patrakov

  parent reply	other threads:[~2007-06-01 16:28 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 [this message]
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

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=46604928.4050002@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --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.