Bruno Haible <br...@clisp.org> 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) into stackbuf? And use the unistring >> equivelent of strlen if DCHAR_T != char? > > Something like this, yes. Fixed through this patch: Ah, I didn't think about DCHAR_CONV_FROM_ENCODING. Patch looks good and I compiled a testdir of all modules clean from warnings. Thanks! Collin
