public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17318] [RFE] Provide a C.UTF-8 locale by default
Date: Wed, 11 Feb 2015 15:39:00 -0000 [thread overview]
Message-ID: <bug-17318-131-9LD6bpjsI0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17318-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17318
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Nick Coghlan from comment #0)
> Fedora doesn't currently provide the C.UTF-8 locale. In the RFE requesting
> it (https://bugzilla.redhat.com/show_bug.cgi?id=902094), it was suggested
> that a more appropriate would be for it to be provided as part of upstream
> glibc, at which point Fedora would inherit it by default.
>
> Hence, this RFE to request the inclusion of a C.UTF-8 locale by default.
>
> My personal interest relates to Python 3, where "LANG=C" misconfigures a few
> aspects to use ASCII, when they really should be using UTF-8. While I'd
> actually like to fix that on the Python side in the long run, being able to
> set "LANG=C.UTF-8" instead is a solution that already works for existing
> versions of Python 3.
>
> Bug #16621 suggests that C.UTF-8 may actually require special casing in
> glibc in order to be handled correctly. If that's accurate, then it would
> strengthen the case for including the locale in the upstream library.
I agree that this is a good idea. Someone needs to do the work and submit it to
libc-alpha. It's not all that easy, and consensus needs to be reached about the
inclusion of ~1.5MB of UTF-8 data into the runtime.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-02-11 15:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 12:57 [Bug libc/17318] New: " ncoghlan at gmail dot com
2014-08-28 7:55 ` [Bug libc/17318] " pbrobinson at gmail dot com
2014-09-10 8:22 ` hadess at hadess dot net
2015-02-10 6:37 ` mcepl at cepl dot eu
2015-02-11 15:39 ` carlos at redhat dot com [this message]
2015-02-17 11:18 ` vapier at gentoo dot org
2015-02-25 23:02 ` ncoghlan at gmail dot com
2015-05-27 7:01 ` myllynen at redhat dot com
2015-08-27 22:23 ` [Bug locale/17318] " jsm28 at gcc dot gnu.org
2015-08-29 20:41 ` vapier at gentoo dot org
2015-08-30 0:49 ` vincent-srcware at vinc17 dot net
2015-09-12 8:30 ` mikaela at mikaela dot info
2020-06-14 23:48 ` ranky at gmx dot net
2020-06-21 14:09 ` carlos at redhat dot com
2020-06-21 14:13 ` carlos at redhat dot com
2020-08-18 14:46 ` carlos at redhat dot com
2020-08-18 15:35 ` carlos at redhat dot com
2020-10-11 11:13 ` aurelien at aurel32 dot net
2020-11-28 16:19 ` accounts+sourceware at carldong dot me
2020-11-28 17:55 ` vincent-srcware at vinc17 dot net
2020-11-30 11:49 ` fweimer at redhat dot com
2020-11-30 12:49 ` mcepl at cepl dot eu
2020-11-30 13:06 ` vincent-srcware at vinc17 dot net
2020-11-30 14:40 ` mcepl at cepl dot eu
2020-11-30 14:41 ` mcepl at cepl dot eu
2020-11-30 16:37 ` vincent-srcware at vinc17 dot net
2021-04-28 16:23 ` carlos at redhat dot com
2021-12-16 21:31 ` carlos at redhat dot com
2021-12-16 21:50 ` carlos at redhat dot com
2021-12-16 21:50 ` carlos at redhat dot com
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=bug-17318-131-9LD6bpjsI0@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).