[Bug localedata/25923] New: Regression: en_US date_fmt and d_t_fmt and "%a %d %b" vs. "%a %b %e"

["carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>]

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

            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 minimum
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.

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