From: DervishD <lkml@dervishd.net>
To: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel utf-8 handling
Date: Sat, 2 Jun 2007 09:43:21 +0200 [thread overview]
Message-ID: <20070602074321.GB20145@DervishD> (raw)
In-Reply-To: <46604928.4050002@ums.usu.ru>
Hi Alexander :)
* Alexander E. Patrakov <patrakov@ums.usu.ru> dixit:
> > 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.
The switch to utf-8 is possible, I know, but I wasn't so sure about
the switch to utf-8 *in the console only*.
> 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.
I was going to take a look at Linux From Scratch (and BLFS, too) for
help, but before trying anything there I wanted to be sure that the
kernel will work. Otherwise I will put my effort in building a minimal X
setup with a suitable terminal emulator.
Anyway, if everything works in the console in the LFS LiveCD, I will
be sure that I can make the change and then I'll look directly in the
LFS book for further instructions.
Thanks a lot! :)
> > 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,
GNU screen? I'll give it a try.
> 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).
There are more terminal emulators for console than I supposed.
> 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).
Well, I'll deal with that issue if I like them more than screen or
plain console.
Thanks again :)
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!
next prev parent reply other threads:[~2007-06-02 7:41 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 [this message]
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=20070602074321.GB20145@DervishD \
--to=lkml@dervishd.net \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
/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