On Tue, 07 Oct 2025 13:15:44 +0200 Bruno Haible <[email protected]> wrote:
> > > 2) a limited amount > > > of Unicode evaluation is available in (IIRC) gnulib > > Correct. The comparison without normalization is available in > libunistring as functions u8_cmp, u16_cmp, u32_cmp > https://www.gnu.org/software/libunistring/manual/html_node/Comparing-Unicode-strings.html > or u8_strcmp, u16_strcmp, u32_strcmp: > https://www.gnu.org/software/libunistring/manual/html_node/Comparing-NUL-terminated-Unicode-strings.html > Whereas the comparison with normalization is available as > functions u8_normcmp, u16_normcmp, u32_normcmp: > https://www.gnu.org/software/libunistring/manual/html_node/Normalizing-comparisons.html > > In Gnulib, each of these functions is available as a Gnulib module: > https://www.gnu.org/software/gnulib/manual/html_node/How-to-use-libunistring.html > https://www.gnu.org/software/gnulib/manual/html_node/_003cunistr_002eh_003e-modules.html > https://www.gnu.org/software/gnulib/manual/html_node/_003cuninorm_002eh_003e-modules.html Bruno, thank your for spelling all that out for me. ISTM we should turn to gnulib. That said, now what? We want to introduce this support both in the compiler (for string literals) and the runtime. Is there something specific I need to do at the gcc level as I introduce this dependency? Do denote the specific modules we're bringing in? It feels like there's machinery I need to engage. "how to use libunistring" says, > You can declare GNU libunistring as a prerequisite of your package for example. --jkl
