On Sat, Mar 30, 2019 at 12:33:32PM +0100, Bruno Haible wrote:
> > It appears that lib/wcwidth.c does actually use uc_width. So the best
> > solution might be to carry on using the wcwidth function in the source
> > code for texi2any (instead of changing this to uc_width), and change the
> > con
Hi Gavin,
> > Different systems have different terminal emulators, and accordingly
> > also different wcwidth functions.
>
> Without knowing anything about the terminal emulators in question, it
> seems to me likely that there would be several terminal emulators with
> different behaviour on t
> From: Gavin Smith
> Date: Sat, 30 Mar 2019 09:27:26 +
> Cc: bug-gnulib@gnu.org, bug-texi...@gnu.org
>
> > 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 l
Thank you for your detailed response.
> Different systems have different terminal emulators, and accordingly
> also different wcwidth functions.
Without knowing anything about the terminal emulators in question, it
seems to me likely that there would be several terminal emulators with
differen
Hi Gavin,
> I wondered if there has been any change since this report:
>
> https://lists.gnu.org/archive/html/bug-gnulib/2008-08/msg00209.html
>
> The issue is that on Solaris 10 and Solaris 11, wcwidth returns 2
> instead of 1 for some characters, for example, opening double quote “.
>
> Some
I wondered if there has been any change since this report:
https://lists.gnu.org/archive/html/bug-gnulib/2008-08/msg00209.html
The issue is that on Solaris 10 and Solaris 11, wcwidth returns 2
instead of 1 for some characters, for example, opening double quote “.
Some of these characters are li
