On 12/18/19 12:21 PM, moos...@gmail.com wrote:
glibc and gnulib behave differently when sv_SE is in effect, the standard (I believe) leaves the behavior unspecified (undefined?) Still The difference is suprising (at least it was to me). Perheaps someone here can comment on the issue?
Traditionally, [a-z] meant to match all characters in the range 'a'..'z' when using native encoding. Long ago some folks tried to change that so that it instead matched all characters collating between 'a' and 'z' inclusive, and glibc and some other libraries implemented things that way. This is now widely viewed to be a mistake, and POSIX now takes no position on the mess (implementations can do whatever they like).
Gnulib attempts to take the traditional meaning (though it doesn't always succeed, I expect). When we have time we are trying to move Gnulib and Glibc back to the original meaning. Code fixes to that effect would be welcome (both in Gnulib and in Glibc, I expect).
