> Date: Mon, 9 Oct 2023 21:17:28 +0200 > From: Patrice Dumas <pertu...@free.fr> > > On Sun, Oct 08, 2023 at 06:29:23PM +0100, Gavin Smith wrote: > > > > I remember that in the past, I broke up some of these lines to avoid > > test failures on some platform that had different wcwidth results for > > some characters. > > Maybe an optionin the long term here would be not to use wcwidth at all, > but use libunistring functions like u8_strwidth. It would probably > remove the issue of locale. The only requirement would be to make sure > that the input string is UTF-8 encoded such that it can be converted to > uint8_t without risk of error.
Isn't makeinfo converts all non-ASCII text to UTF-8 anyway? If so, we should always use the UTF-8 functions, without relying on the locale and libc locale-aware functions.
