Re: Variant wcwidth results on Solaris

[Eli Zaretskii]

> From: Gavin Smith <address@hidden>
> Date: Sat, 30 Mar 2019 09:27:26 +0000
> Cc: address@hidden, address@hidden
> 
> > Another approach is to not include the code from gnulib, but instead
> > rely on a preinstalled GNU libunistring. For this, use the gnulib
> > module 'libunistring'.
> 
> libunistring looks like a very useful library, and I was not aware of 
> it.  There is no reference to this library in the gnulib manual or the 
> glibc manual.  Should a note be added to 
> doc/posix-functions/wcwidth.texi saying that libunistring should be used 
> if you want to get consistent results across systems?

libunistring comes with its own Info manual, FWIW.

I'm not sure I understand what you want to use libunistring for in
Texinfo, but I just wanted to tell that some old versions of that
library (before 0.9.4, I think?) were quite useless on MS-Windows,
because the locale and its codeset for any non-default locale were
incorrectly determined.  See this thread:

  https://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00003.html

So if you decide to use the installed version of libunistring, and the
issues described in the above thread are pertinent, we should watch
for those old versions on MS-Windows.