Collin Funk wrote:
> Just curious, do you do a libunistring release roughly around each new
> Unicode standard release?
Each major Unicode standard release, yes. For minor Unicode standard updates,
it depends.
> >> And copy nl_langinfo (THOUSEP) into stackbuf? And use the unistring
> >> equivelen
Bruno Haible writes:
> Thanks a lot for this report! Without you, I would not have noticed,
> possibly not even before the next libunistring release.
Glad to help.
Just curious, do you do a libunistring release roughly around each new
Unicode standard release?
>> And copy nl_langinfo (THOUSEP)
Hi Collin,
> Bruno Haible via Gnulib discussion list writes:
>
> > This patch fixes it, by considering the 'grouping' sequence of numbers.
>
> On FreeBSD 15.0 (cfarm427) I see the following warnings:
>
> In file included from unistdio/u16-u16-vasnprintf.c:57:
> ./vasnprintf.c:5224:77:
Hi Bruno,
Bruno Haible via Gnulib discussion list writes:
> This patch fixes it, by considering the 'grouping' sequence of numbers.
On FreeBSD 15.0 (cfarm427) I see the following warnings:
In file included from unistdio/u16-u16-vasnprintf.c:57:
./vasnprintf.c:5224:77: warning: incompat
Tested by rebuilding coreutils with the newest gnulib,
configuring it through
gl_cv_func_printf_precision=no gl_cv_func_printf_enomem=no ./configure
on a glibc system, and then running
$ LC_ALL=ta_IN ./printf "%'.0f\\n" 11234567890
Previous (wrong) result:
1,111,111,111,234,567,890
Ne
