public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
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 06:20:00 -0000 [thread overview] Message-ID: <bug-16621-131-4Mn3jBMTw3@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16621-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16621 --- Comment #7 from Nick Coghlan <ncoghlan at gmail dot com> --- I filed #17318 because Fedora doesn't want to add C.UTF-8 independently of upstream glibc (at least in part to avoid inconsistencies like the one reported here). However, I also interpret the current bug closure as categorically rejecting the notion of treating C.UTF-8 the same as the C locale when it comes to the LANGUAGE variable, which doesn't seem like the correct outcome. If I've misunderstood what "CLOSED INVALID" means and the intent is for bug #17318 to include the behaviour requested here, then yes, I would consider that a reasonable way to resolve this issue. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-08-30 6:20 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-21 12:47 [Bug libc/16621] New: " vincent-srcware at vinc17 dot net 2014-02-21 13:41 ` [Bug libc/16621] " vincent-srcware at vinc17 dot net 2014-06-13 9:20 ` fweimer at redhat dot com 2014-08-27 12:59 ` ncoghlan at gmail dot com 2015-08-27 22:20 ` [Bug locale/16621] " jsm28 at gcc dot gnu.org 2015-08-29 20:41 ` vapier at gentoo dot org 2015-08-30 5:59 ` vapier at gentoo dot org 2015-08-30 6:20 ` ncoghlan at gmail dot com [this message] 2021-12-16 21:31 ` carlos at redhat dot com 2022-08-02 10:36 ` nl6720 at gmail dot com 2022-08-02 11:38 ` vincent-srcware at vinc17 dot net 2022-08-02 11:39 ` vincent-srcware at vinc17 dot net 2022-08-02 13:40 ` fweimer at redhat dot com 2022-08-02 14:17 ` vincent-srcware at vinc17 dot net 2022-08-02 14:30 ` fweimer at redhat dot com 2022-08-02 15:15 ` vincent-srcware at vinc17 dot net 2022-08-04 20:46 ` jwilk at jwilk dot net 2022-11-14 13:01 ` fweimer at redhat dot com 2023-09-04 13:29 ` fweimer at redhat dot com 2023-09-04 13:32 ` fweimer at redhat dot com 2023-11-20 15:03 ` cvs-commit at gcc dot gnu.org
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-16621-131-4Mn3jBMTw3@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: linkBe 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).