Jeff Davis <pg...@j-davis.com> writes: > What should we do with locales like C.UTF-8 in both libc and ICU?
I vote for passing those to the existing C-specific code paths, whereever we have any (not sure that we do for <ctype.h> functionality). The semantics are quite well-defined and I can see no good coming of allowing either provider to mess with them. > If we capture it like the C locale, then where do we draw the line? Any > locale that begins with "C."? What if the language part is C but there > is some other part to the locale? What about lower case? Should all of > these apply the same way except with POSIX? What about backwards > compatibility? Probably "C", or "C.anything", or "POSIX", or "POSIX.anything". Case-independent might be good, but we haven't accepted such in the past, so I don't feel strongly about it. (Arguably, passing lower case "c" to the provider would provide an "out" to anybody who dislikes our choices here.) regards, tom lane