https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #222 from RJVB <rjvber...@gmail.com> --- Doesn't Qt have to be configured to use ICU, or is that only on non-linux/unix platforms (Mac included)? ICU uses hardcoded locale definitions? FWIW, the specialty library approach I mentioned could of course provide suitably amended forks of the ICU and/or libc/POSIX locale functions, which would override those in ICU and/or libc. Doing this carefully enough it should be possible to avoid risk of ODR/ABI issues - I suppose. Heck, the new behaviour could even be conditional on something like an env. variable that "deviant" users like us would have to set. I agree that ICU nor POSIX are likely to change their implementations without a sufficient body of evidence that an alternative implementation is backwards compatible in ABI, API *and* behavioural terms. With enough evidence of demand for an optional different behaviour, however, they could not reject a merge request as introducing unjustified code complexification... -- You are receiving this mail because: You are watching all bug changes.
