From owner-freebsd-current@FreeBSD.ORG Thu Jun 17 02:10:14 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B21441065675 for ; Thu, 17 Jun 2010 02:10:14 +0000 (UTC) (envelope-from gaijin.k@ovi.com) Received: from outbound2.messaging.lotuslive.com (outbound2.messaging.lotuslive.com [8.12.152.118]) by mx1.freebsd.org (Postfix) with ESMTP id 8C92D8FC12 for ; Thu, 17 Jun 2010 02:10:14 +0000 (UTC) Received: from outbound2.messaging.lotuslive.com (44.32.6.10.in-addr.arpa [10.6.32.44]) by c-in3ofal02-02.sv2.lotusliveops.com (Postfix) with ESMTP id CE33811B0BB8 for ; Thu, 17 Jun 2010 01:58:15 +0000 (GMT) Received: from c-in3ofil02-02.sv2.lotusliveops.com (49.32.6.10.in-addr.arpa [10.6.32.49]) by c-in3obnd02-02.sv2.lotusliveops.com (Postfix) with ESMTP id D1D6F2FEB5 for ; Thu, 17 Jun 2010 01:58:14 +0000 (GMT) Received: from 80.32.6.10.in-addr.arpa (c-in3ws--02-05.sv2.lotusliveops.com [10.6.32.80]) (sender gaijin.k@ovi.com) by c-in3ofil02-02.sv2.lotusliveops.com (LotusLive iNotes outfilter/0.91) with SMTP; Thu, 17 Jun 2010 01:58:14 +0000 Received: (qmail 23235 invoked from network); 17 Jun 2010 01:58:14 -0000 Received: from unknown (HELO c-in3play02-02.sv2.lotusliveops.com) (gaijin.k@ovi.com@74.105.210.169) by 80.32.5.10.in-addr.arpa with SMTP; 17 Jun 2010 01:58:14 -0000 From: "Alexandre \"Sunny\" Kovalenko" To: Anton Shterenlikht In-Reply-To: <20100616163035.GA42606@mech-cluster241.men.bris.ac.uk> References: <20100616131503.GA77642@mech-cluster241.men.bris.ac.uk> <20100616134530.GX1797@hoeg.nl> <20100616163035.GA42606@mech-cluster241.men.bris.ac.uk> Content-Type: multipart/mixed; boundary="=-RZXOaD/MUq/1qj/00m7C" Date: Wed, 16 Jun 2010 21:57:22 -0400 Message-ID: <1276739842.66339.15.camel@RabbitsDen> MIME-Version: 1.0 X-Mailer: Evolution 2.30.1.2 FreeBSD GNOME Team Port X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: how to set up UTF8 russian in -current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 02:10:14 -0000 --=-RZXOaD/MUq/1qj/00m7C Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 2010-06-16 at 17:30 +0100, Anton Shterenlikht wrote: > On Wed, Jun 16, 2010 at 03:45:30PM +0200, Ed Schouten wrote: > > * Anton Shterenlikht wrote: > > > My system is amd64 r209195. > > >=20 > > > I was wondering if the user localisation > > > section of the handbook is a bit out of date: > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/using-local= ization.html > > >=20 > > > The handbook suggests using cons25r, whereas > > > the default console type in /etc/ttys is now xterm. > > > And keeping cons25r together with relevant fonts, > > > screenmap and keymap in /etc/rc.conf doesn't seem > > > to work anymore. > > >=20 > > > Also, the latest I can find on UTF8 in FreeBSD > > > is this thread: > > > http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009349.h= tml > > >=20 > > > I tried to follow the advice given in this thread, > > > namely I've rebuilt the kernel with TEKEN_UTF8 > > > (it seems the other option mentioned, TEKEN_XTERM, is no > > > longer valid), and set LC_CTYPE=3Dru_RU.UTF-8 > > > in my shell. This didn't seem to have any effect. > >=20 > > Even though UTF-8 support for the console is closer than it used to be, > > it's still not useful in practice, since syscons won't display it. I > > guess if you want to get Russian working on HEAD, you should do the > > following: > >=20 > > - Don't set TEKEN_* in your kernel configuration file. > > - Just use the xterm terminal type in /etc/ttys. > > - Set LC_CTYPE=3Dru_RU.{CP1251,CP866,ISO8859-5,KOI8-R}. > > - Load a font for Syscons which uses the same character as the one you > > chose above. > >=20 > > So this means 8-bit character sets is the best thing we can do right > > now. >=20 > Yes, this works fine. > I guess TEKEN_* in the kernel broke it. >=20 > However, russian in xterm is still not working. > This is probably my misconfiguration.. Can you specifically point out things that do not work for you in the xterm window? I am able to create files and directories with Cyrillic names, use Cyrillic strings as the command parameters, etc. It has been working for me for quite a long time, so I could not really remember what, if anything, I had to do, but we can compare settings if you'd like to. I do use Gnome, though, so some of its pixie dust could have been spilled onto xterm. I have attached small screenshot as an illustration -- if this is not what you are talking about, please, accept my apology for the noise. >=20 > many thanks for your help > anton >=20 >=20 --=20 Alexandre Kovalenko (=D0=9E=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=80= =D0=9A=D0=BE=D0=B2=D0=B0=D0=BB=D0=B5=D0=BD=D0=BA=D0=BE) -------------------------------------------------------------- Ovi Store: Fresh apps and more http://store.ovi.com/?cid=3Dovistore-fw-bac-na-acq-na-ovimail-g0-na-4 --=-RZXOaD/MUq/1qj/00m7C--