From: Matthias Maier <tamiko@43-1.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Arfrever Frehtes Taifersar Arahesis" <arfrever.fta@gmail.com>,
qemu-devel@nongnu.org, "Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] Partially revert commit d4e5ec877ca
Date: Fri, 15 Jun 2018 10:51:19 -0500 [thread overview]
Message-ID: <87d0wsqc94.fsf@43-1.org> (raw)
In-Reply-To: <87h8m4yt8b.fsf@dusky.pond.sub.org> (Markus Armbruster's message of "Fri, 15 Jun 2018 17:17:24 +0200")
On Fri, Jun 15, 2018, at 10:17 CDT, Markus Armbruster <armbru@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/
next prev parent reply other threads:[~2018-06-15 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 4:40 [Qemu-devel] [PATCH v2 0/2] Fix compilation with python-3 if en_US.UTF-8 is unavailable Matthias Maier
2018-06-15 4:40 ` [Qemu-devel] [PATCH v2 1/2] Partially revert commit d4e5ec877ca Matthias Maier
2018-06-15 9:42 ` Daniel P. Berrangé
2018-06-15 13:20 ` Matthias Maier
2018-06-15 15:17 ` Markus Armbruster
2018-06-15 15:51 ` Matthias Maier [this message]
2018-06-15 15:20 ` Daniel P. Berrangé
2018-06-15 4:40 ` [Qemu-devel] [PATCH v2 2/2] qapi: open files in binary mode and use explicit decoding/encoding in common.py Matthias Maier
2018-06-15 15:31 ` Markus Armbruster
2018-06-15 21:55 ` Matthias Maier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0wsqc94.fsf@43-1.org \
--to=tamiko@43-1.org \
--cc=arfrever.fta@gmail.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.