HEADS UP: ncurses is updated

[Nikolay Pavlov]

On Monday,  9 April 2007 at 11:48:08 -0700, Jeremy Chadwick wrote:
> On Mon, Apr 09, 2007 at 11:21:08AM -0700, Jeremy Chadwick wrote:
> > On Tue, Apr 10, 2007 at 01:49:32AM +0800, Rong-en Fan wrote:
> > > On 4/10/07, Jeremy Chadwick <koitsu at freebsd.org> wrote:
> > > >The only thing I've found, though, is that dialog(1) does not appear to
> > > >properly handle UTF-8 encoding.  Line drawing characters show up as
> > > >gibberish (alphanumeric characters).  I realise dialog isn't part of
> > > >ncurses, but it does rely on it.  We should consider updating dialog to
> > > >match this change.
> > > 
> > > You mean it display sometihng like "tqxu" instead of line drawing 
> > > characters?
> > > Last time I checked, I thought it is terminal related. When I use screen, it
> > > uses line drawing character. For PuTTY, see:
> > > 
> > > http://lists.freebsd.org/pipermail/freebsd-questions/2007-April/146577.html
> 
> This is quite applicable.  I just now got around to reading it
> (should've done this before I sent my previous Email).  Yep, that's the
> exact problem:
> 
> /usr/bin/dialog:
> 	libdialog.so.5 => /usr/lib/libdialog.so.5 (0x3807e000)
> 	libncurses.so.6 => /lib/libncurses.so.6 (0x38099000)
> 	libc.so.6 => /lib/libc.so.6 (0x380dd000)
> 
> At least I have a workaround with NCURSES_NO_UTF8_ACS=1.  :-)

I am not sure, but maybe this is related to ncurses update. I am getting
this trying to run sysinstall utility:

Probing devices, please wait (this can take a while)...BARF 170 <105>

Than goes EOL and exit...

It's a current from April 6.

-- 
======================================================================  
- Best regards, Nikolay Pavlov. <<<-----------------------------------    
======================================================================