public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/17318] [RFE] Provide a C.UTF-8 locale by default
Date: Sun, 30 Aug 2015 00:49:00 -0000	[thread overview]
Message-ID: <bug-17318-131-3efQsd3zfD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17318-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17318

Vincent Lefèvre <vincent-srcware at vinc17 dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vincent-srcware at vinc17 dot net

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-29587-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sun Aug 30 04:38:27 2015
Return-Path: <glibc-bugs-return-29587-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 114677 invoked by alias); 30 Aug 2015 04:38:24 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 114638 invoked by uid 48); 30 Aug 2015 04:38:20 -0000
From: "ncoghlan at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/16621] C.UTF-8 locales should be regarded like C w.r.t. $LANGUAGE precedence
Date: Sun, 30 Aug 2015 04:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: locale
X-Bugzilla-Version: 2.18
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ncoghlan at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16621-131-VYMpS7c7Vl@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16621-131@http.sourceware.org/bugzilla/>
References: <bug-16621-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-08/txt/msg00627.txt.bz2
Content-length: 974

https://sourceware.org/bugzilla/show_bug.cgi?id\x16621

--- Comment #5 from Nick Coghlan <ncoghlan at gmail dot com> ---
While it's true that glibc itself doesn't provide a C.UTF-8 locale, does that
really make this bug report invalid?

The Debian-derived family of distros default to adding a C.UTF-8 locale at the
distro level, but it doesn't quite work as expected, as it's missing some of
the special casing afforded the default C locale. The specific one covered by
this BZ is the face that LC_ALL=C will make glibc ignore the LANGUAGE setting,
but LC_ALL=C.UTF-8 doesn't.

Another possible way of phrasing the request would be for all "C.*" locales to
ignore the LANGUAGE setting the same way the unmodified "C" locale does, rather
than special casing "C.UTF-8". I'm not *personally* aware of any such locales
in widespread use other than "C.UTF-8", but that doesn't mean there aren't any.

--
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-08-30  0:49 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
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 [this message]
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-3efQsd3zfD@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).