On Mon, 13 Jul 2020, Geoff Clare wrote:
J William Piggott <elseift...@gmx.com> wrote, on 12 Jul 2020:
On Mon, 6 Jul 2020, Geoff Clare wrote:
There is no way we are going to change the required d_t_fmt value for
the POSIX locale.
Why?
Because every implementation would have to change, and all applications
that rely on the current value would potentially break (depending on
which fields they use).
What implementation would have to change? The locale database assigned
values change on a regular basis. I would not call that an
implementation change.
I would be surprised if any breakage would happen by adding the time
zone to the POSIX locale's date-and-time format string. Do you have an
example of something that would break (other than compliance tests)?
I have been searching source code and have not found any direct use of
d_t_fmt (%c). At one time util-linux hwclock(8) used %c as its default
output, but I changed it to ISO 8601. I expected pushback that I had
broken something. That was about 5 years ago and, as far as I know,
there never have been any complaints.
We would need a very good reason to make such a change.
Clearly you disagree, but I think this is a very good reason.
Has it been discussed with 'we'? Would any of them like to comment on
this please?
I've been using "we" to refer to the whole Austin Group, i.e. everyone
on this mailing list, so yes it has been discussed (in this thread).
The three people who's opinions matter are the organisational
representatives who would vote on it if it came to that. I'm sure if
any of them disagree with what I've said they will comment.
--
Geoff Clare <g.cl...@opengroup.org>
The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
