On Fri, Jun 15, 2018, at 10:17 CDT, Markus Armbruster <arm...@redhat.com> wrote:
> "Partially revert"? Which part isn't reverted? Yes, it ended up being a full revert of the commit in question. I am sorry for the sloppy wording. > [...] >> Recently, however, glibc introduced a new locale "C.utf-8" that just >> uses UTF-8 as its charset, but otherwise leaves the semantics alone. >> Just setting the right character set is enough for our use case, so we >> can just hardcode this one without having to be afraid of nasty side >> effects. > Looks like your frustration about upstream glibc is quite stale :) Unfortunately, this statement is not correct. The corresponding glibc bug report summarizes the current situation [1]. Fact is that a lot of distributions ship a custom C.UTF-8 locale, for example Debian [2] (for the currenct glibc-2.27 release). Unfortunately, not everyone applies such custom patches. :-/ Best, Matthias [1] https://sourceware.org/bugzilla/show_bug.cgi?id=17318 [2] https://sources.debian.org/patches/glibc/2.27-3/localedata/locale-C.diff/
