Re: [Heads up] TERM=xterm is now the default (on non-i386)

Hi 

Any chance to get it fixed somehow ? 

midnight commander does not work correctly even with no screen-maps,
vidcontrol -T xterm, env TERM=xterm LANG=ru_RU.UTF-8


also, console does not handle correctly multi-byte utf-8 characters
(it should already or not ?) 


-----Original Message-----
From: Andrey Chernov <ache_at_nagual.pp.ru>
To: Ed Schouten <ed_at_80386.nl>
Cc: FreeBSD Current <current_at_freebsd.org>
Subject: Re: [Heads up] TERM=xterm 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,
> 
> 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 
missing (i.e. default) ac= termcap capability (f.e. in tzsetup etc.)
There are 2 ways to fix it.
1) Make separate xterm-r with corrected ac= (that way is ugly).
2) Don't seek for vt100 pseudographics in loaded font at all, just use 
internal kernel font.
Please decide how to fix this better. For now only fallback to '-T cons25' 
is solution for Russian users.



-- 
Vladimir B. Grebenschikov
vova_at_fbsd.ru