From: Mike FABIAN <mfabian@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: 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 14:11:07 +0100 [thread overview]
Message-ID: <s9dlgtr8jdg.fsf@redhat.com> (raw)
In-Reply-To: <w51mve7o4n1.fsf@maestria.local.igalia.com> (Alberto Garcia's message of "Tue, 31 Jan 2017 12:22:42 +0100")
Alberto Garcia <berto@igalia.com> さんはかきました:
> 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.
Both work:
mfabian@taka:~
$ LC_ALL=C.utf-8 strace -eopen ls 2>&1 | grep LC_CTYPE
open("/usr/lib/locale/C.utf-8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/C.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3
mfabian@taka:~
$ LC_ALL=C.UTF-8 strace -eopen ls 2>&1 | grep LC_CTYPE
open("/usr/lib/locale/C.UTF-8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/C.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3
mfabian@taka:~
$ LC_ALL=C.UTF8 strace -eopen ls 2>&1 | grep LC_CTYPE
open("/usr/lib/locale/C.UTF8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/C.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3
mfabian@taka:~
$ LC_ALL=C.utf8 strace -eopen ls 2>&1 | grep LC_CTYPE
open("/usr/lib/locale/C.utf8/LC_CTYPE", O_RDONLY|O_CLOEXEC) = 3
mfabian@taka:~
$
I like C.UTF-8 because “UTF-8” is the official spelling
of that encoding:
https://en.wikipedia.org/wiki/UTF-8#Official_name_and_variants
Using “C.utf8” uses one stat less though because it is the last
fallback, as you can see in the strace.
> - When was this added? This bug seems to be still open:
> https://sourceware.org/bugzilla/show_bug.cgi?id=17318
Fedora has it since Fedora 24 (spring 2016), Debian for a while longer.
I’ll ping again to get it included upstream.
It needs 1.5MB at runtime only because of
https://sourceware.org/bugzilla/show_bug.cgi?id=18978
as soon as that sorting bug is fixed, the C.UTF-8 locale will need
less than 200k.
> Berto
--
Mike FABIAN <mfabian@redhat.com>
睡眠不足はいい仕事の敵だ。
next prev parent reply other threads:[~2017-01-31 13:11 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 [this message]
2017-01-31 13:23 ` Alberto Garcia
2017-01-31 13:59 ` Eric Blake
2017-01-31 16:05 ` Mike FABIAN
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=s9dlgtr8jdg.fsf@redhat.com \
--to=mfabian@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.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 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.