public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat 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: Tue, 02 Aug 2022 13:40:30 +0000 [thread overview] Message-ID: <bug-16621-131-euvE699Ald@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16621-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16621 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com --- Comment #10 from Florian Weimer <fweimer at redhat dot com> --- C is special-cased here: /* Ignore LANGUAGE and its system-dependent analogon if the locale is set to "C" because 1. "C" locale usually uses the ASCII encoding, and most international messages use non-ASCII characters. These characters get displayed as question marks (if using glibc's iconv()) or as invalid 8-bit characters (because other iconv()s refuse to convert most non-ASCII characters to ASCII). In any case, the output is ugly. 2. The precise output of some programs in the "C" locale is specified by POSIX and should not depend on environment variables like "LANGUAGE" or system-dependent information. We allow such programs to use gettext(). */ if (strcmp (locale, "C") == 0) return locale; It looks like the locale name is not embedded in the locale data itself, so identifying C.UTF-8 based on its name might not be so simple here. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-02 13:40 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 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 [this message] 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-euvE699Ald@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).