I will check this. Most likely we could support wide character.

Stefan Teleman wrote:
>
>
> Danek Duvall wrote:
>> Has any thought been given to replacing Solaris curses with ncurses?  I
>> believe that ncurses claims to be completely compatible with System V
>> curses, and given that it's actually kept up-to-date, and is 
>> generally more
>> featureful than Solaris curses, it would likely be a good move.
>>
>>
>> On Fri, Aug 15, 2008 at 12:59:47AM -0700, Shi-Ying Irene Huang wrote:
>>
>>>                 /usr/lib/libgcurses.so
>>>                 /usr/lib/libgform.so.5
>>>                 /usr/lib/libgmenu.so.5
>>>                 /usr/lib/libgncurses.so.5
>>>                 /usr/lib/libgpanel.so.5
>>>                                      Volatile         Supporting 
>>> libraries                                                        
>>> These are files with a 'g' prefix
>>
>> Are any of these names used by anyone, anywhere?  Is there any value in
>> shipping them?  You are, however, missing the most important one --
>> /usr/lib/libncurses.so.5 -- which is what everyone is going to expect.
>>
>>>                 /usr/gnu/lib/libcurses.so
>>>                 /usr/gnu/lib/libform.so.5
>>>                 /usr/gnu/lib/libmenu.so.5
>>>                 /usr/gnu/lib/libncurses.so.5
>
> Questions:
>
> Is ncurses being compiled with wide char/UTF support ?
>
> If it is, the name of the libraries is usually set to libncursesw.so, 
> libtinfow.so, libformw.so, etc.
>
> If it is not, wide char/UTF support will not be available.
>


> Also, terminfo support in ncurses is based on two mechanisms:
>
> 1. directory based ( ${prefix}/share/terminfo/* )
> 2. Berkeley DB based (terminfo.db)
>
> The Berkeley DB based implementation is usually slower (and creates a 
> dependency  on Berkeley DB).
>
> --Stefan
>


Reply via email to