From: Mike FABIAN <mfabian@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Alberto Garcia <berto@igalia.com>, Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, armbru@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH] gtk: Hardcode LC_CTYPE as C.utf-8
Date: Tue, 31 Jan 2017 17:05:09 +0100 [thread overview]
Message-ID: <s9dy3xr6wqy.fsf@redhat.com> (raw)
In-Reply-To: <e4864049-0a56-bd97-4cd4-c71878a8477f@redhat.com> (Eric Blake's message of "Tue, 31 Jan 2017 07:59:07 -0600")
Eric Blake <eblake@redhat.com> さんはかきました:
> On 01/31/2017 05:22 AM, Alberto Garcia wrote:
>> On Tue 31 Jan 2017 11:09:45 AM CET, Kevin Wolf <kwolf@redhat.com> wrote:
>>
>>> 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.
>>
>>> setlocale(LC_MESSAGES, "");
>>> + setlocale(LC_CTYPE, "C.utf-8");
>>> bindtextdomain("qemu", CONFIG_QEMU_LOCALEDIR);
>>
>> A couple of quick questions:
>>
>> - Is it C.utf-8 or C.UTF-8 ? 'locale -a' shows only the latter in my
>> system.
>
> At least Cygwin has C.UTF-8, but not C.utf-8. Furthermore, since my
> system defaults to en_US.UTF-8, I would expect the upper-case variant
> for the character set name across all locales.
Yes, I think it is more compatible to use the C.UTF-8 spelling because
it uses the “official” spelling of “UTF-8”.
--
Mike FABIAN <mfabian@redhat.com>
睡眠不足はいい仕事の敵だ。
next prev parent reply other threads:[~2017-01-31 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 10:09 [Qemu-devel] [PATCH] gtk: Hardcode LC_CTYPE as C.utf-8 Kevin Wolf
2017-01-31 11:22 ` Alberto Garcia
2017-01-31 13:11 ` Mike FABIAN
2017-01-31 13:23 ` Alberto Garcia
2017-01-31 13:59 ` Eric Blake
2017-01-31 16:05 ` Mike FABIAN [this message]
2017-01-31 13:04 ` Gerd Hoffmann
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=s9dy3xr6wqy.fsf@redhat.com \
--to=mfabian@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).