Hello, > Does "wide character" refer to double-width characters such as Chinese > characters, or is it support for the wchar_t type?
I do not know. The proposed patch does work. But I think that adding w to the library names changes the API. The truth is - I do not know it, but I my guess is that libtinfow and libtinfo are not interchangeable, otherwise they would not had different names. Greetings Дилян -----Original Message----- From: Gavin Smith <[email protected]> To: Дилян Палаузов <[email protected]> Cc: [email protected] Subject: Re: texinfo 7.2 does not utilize libinfow Date: 18/06/25 18:52:39 On Wed, Jun 18, 2025 at 09:28:25AM +0300, Дилян Палаузов wrote: > Hello, > > libtinfo and libtinfow are created from the source code of ncurses. When > there ./configure is called with --enable-widec then the w libraries are > generated - libticw, libformw, libncursesw, libtinfow. > > These libraries I guess support both narrow and wide characters, while the > no-w libraries cannot handle wide characters. > > Greetings > Дилян Thanks for the explanation. Can you check if the following allows Texinfo to build with "info" being built? diff --git a/configure.ac b/configure.ac index 3c31b75b41..92ee23ef85 100644 --- a/configure.ac +++ b/configure.ac @@ -206,7 +206,7 @@ AM_CONDITIONAL(TOOLS_ONLY, [[test "x$tools_only" = x1]]) # rather ncurses. So we check for it. TERMLIBS= # Check for termlib before termcap because Solaris termcap needs libucb. -TERMLIB_VARIANTS="tinfo ncurses curses termlib termcap terminfo" +TERMLIB_VARIANTS="tinfo tinfow ncurses ncursesw curses termlib termcap terminfo" for termlib in ${TERMLIB_VARIANTS}; do AC_CHECK_LIB(${termlib}, tgetent, [TERMLIBS="${TERMLIBS} -l${termlib}"; break]) Also, do you have any idea what our preference order should be for checking these libraries? E.g. would some be simpler or more reliable than others? Does "wide character" refer to double-width characters such as Chinese characters, or is it support for the wchar_t type?
