Date: Sun, 13 Dec 2009 18:33:22 +0300 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Andrey Chernov <ache@nagual.pp.ru> Cc: Ed Schouten <ed@80386.nl>, FreeBSD Current <current@freebsd.org> Subject: Re: [Heads up] TERM=xterm is now the default (on non-i386) Message-ID: <1260718402.2505.37.camel@localhost> In-Reply-To: <20091130044130.GA55612@nagual.pp.ru> References: <20091111101207.GF64905@hoeg.nl> <20091113060021.GW64905@hoeg.nl> <20091130044130.GA55612@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi=20 Any chance to get it fixed somehow ?=20 midnight commander does not work correctly even with no screen-maps, vidcontrol -T xterm, env TERM=3Dxterm LANG=3Dru_RU.UTF-8 also, console does not handle correctly multi-byte utf-8 characters (it should already or not ?)=20 -----Original Message----- From: Andrey Chernov <ache@nagual.pp.ru> To: Ed Schouten <ed@80386.nl> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: [Heads up] TERM=3Dxterm is now the default (on non-i386) Date: Mon, 30 Nov 2009 07:41:30 +0300 On Fri, Nov 13, 2009 at 07:00:21AM +0100, Ed Schouten wrote: > Hi folks, >=20 > I just committed the previously mentioned patch to SVN. Please refer to > the last part of the commit message to see what you can do when you run > into trouble. It seems xterm emulator can't co-exist with screen maps, namely vidcontrol -l koi8-r2cp866 I got Russian letters everywhere instead of vt100 pseudographics due to=20 missing (i.e. default) ac=3D termcap capability (f.e. in tzsetup etc.) There are 2 ways to fix it. 1) Make separate xterm-r with corrected ac=3D (that way is ugly). 2) Don't seek for vt100 pseudographics in loaded font at all, just use=20 internal kernel font. Please decide how to fix this better. For now only fallback to '-T cons25'=20 is solution for Russian users. --=20 Vladimir B. Grebenschikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1260718402.2505.37.camel>