On Mon, Nov 13, 2023 at 10:28:35AM +0100, Patrice Dumas wrote: > According to your mail > https://lists.gnu.org/archive/html/bug-libunistring/2023-11/msg00000.html > > char32_t is less portable, and indeed, the solaris automatic build sees > to fail because of char32_t is not available, while uint32_t and ucs4_t > are necessarily present with libunistring unless I issed something. So > it would probably be more portable to use uint32_t/ucs4_t, though it may > be less practical if a conversion is needed before they can be used.
I've imported the "uchar" gnulib module so that the char32_t type will be defined in uchar.h. "uchar" seems significantly less bloated that "uchar-c23" and not sure if "uchar-c23" is necessary for our purposes.
