From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 63CA3388F403; Tue, 5 May 2020 13:57:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 63CA3388F403 From: "carlos at redhat dot com" To: libc-locales@sourceware.org Subject: [Bug localedata/25923] New: Regression: en_US date_fmt and d_t_fmt and "%a %d %b" vs. "%a %b %e" Date: Tue, 05 May 2020 13:57:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: NEW 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: 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 X-BeenThere: libc-locales@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-locales mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2020 13:57:07 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D25923 Bug ID: 25923 Summary: Regression: en_US date_fmt and d_t_fmt and "%a %d %b" vs. "%a %b %e" Product: glibc Version: 2.29 Status: NEW Severity: normal Priority: P2 Component: localedata Assignee: unassigned at sourceware dot org Reporter: carlos at redhat dot com CC: libc-locales at sourceware dot org Target Milestone: --- In commit 7395f3a0efad9fc51bb54fa383ef6524702e0c49, which is discussed here: https://sourceware.org/pipermail/libc-alpha/2018-December/100227.html The date_fmt was defined for en_US to correct the 24h clock issue. What was not discussed at the time, perhaps overlooked, is that the display order of the month and day was changed. For 20 years date_fmt has printed: date +"%a %b %e" Tue May 5 For 23 years d_t_fmt has printed: date +"%a %d %b" Tue 05 May When commit 7395f3a0efad9fc51bb54fa383ef6524702e0c49 fixed the 24h change it also changed the month and day ordering. This is a change in behaviour that should be discussed. We should at a mini= mum revert the monty and day ordering change until we can agree what should be = done for date_fmt or d_t_fmt. My opinion is that we should minimize the amount of change being done, and simply keep d_t_fmt and date_fmt different, but retain the fixed 12h clock = as intended by the original fix for bug 24046. --=20 You are receiving this mail because: You are on the CC list for the bug.=