From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id A230C3858C00; Sat, 12 Nov 2022 01:35:40 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A230C3858C00
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1668216940;
	bh=lIIMqGnFEamIKSULzjMRMpt8kBO0ZBSGVhzcxSSqJUg=;
	h=From:To:Subject:Date:From;
	b=a4Rqe//FWiroABC+/8YwApfLNc6PklVOqTtvfXn3PQzC9K3RMjDnGULo22q+6vVrN
	 4uOa9dXCA5OptwaZIqhqvR/5ZExLjHNJvBqqXXYS+C4vo2qGXRIfUWtxteQUjI0Cxh
	 E1nS3r7FLuCPgt5qw5rICg//F/6jbvfO6DHprQ44=
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29777] New: LANGUAGE interpretation in C.UTF-8 locale is
 not like in C locale
Date: Sat, 12 Nov 2022 01:35:40 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.35
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bruno at clisp dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-29777-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <glibc-bugs.sourceware.org>

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

            Bug ID: 29777
           Summary: LANGUAGE interpretation in C.UTF-8 locale is not like
                    in C locale
           Product: glibc
           Version: 2.35
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: bruno at clisp dot org
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

The C.UTF-8 locale was introduced in glibc 2.35, see
https://sourceware.org/pipermail/libc-announce/2022/000033.html

Unfortunately, it is undocumented. As a fallback, I assume that the wiki pa=
ge
https://sourceware.org/glibc/wiki/Proposals/C.UTF-8 , which carries the mar=
ker
"Merged for glibc 2.35", describes the intention.

This wiki page states "Setting LC_ALL=3DC.UTF-8 will ignore LANGUAGE just l=
ike it
does with LC_ALL=3DC. See guess_category_value() in intl/dcigettext.c and h=
ow it
checks "C" for more details."

But this is not how it behaves.

How to reproduce:
In a Fedora 36 installation:

$ /lib64/libc.so.6 --version

tells me that I'm using glibc 2.35.

$ locale -a | grep ^C
C
C.utf8

This shows that the C.UTF-8 locale is installed.

$ LC_ALL=3DC.UTF-8 LANGUAGE=3Dfr ls --help
shows a help text in French, taken from
/usr/share/locale/fr/LC_MESSAGES/coreutils.mo .

But the expected output, per the wiki page above, is the English (untransla=
ted)
help text.

The attached patch fixes it for me, when applied to gettext's libintl libra=
ry,
with an 'ls' binary that links against libintl. I expect this patch will wo=
rk
in the same way from within glibc.

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