From: Michael Hudson-Doyle via Libc-alpha <libc-alpha@sourceware.org>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v12 2/2] Add generic C.UTF-8 locale (Bug 17318)
Date: Mon, 31 Jan 2022 12:58:17 +1300 [thread overview]
Message-ID: <CAJ8wqtfnFF71bKhLVGe=g5fjWwGRTprGLQW-5tPCOyjJchHUaQ@mail.gmail.com> (raw)
In-Reply-To: <a2ff9a8e-60cf-b791-80a3-6ef145c608ad@redhat.com>
On Sat, 29 Jan 2022 at 05:42, Carlos O'Donell <carlos@redhat.com> wrote:
> On 1/25/22 21:44, Michael Hudson-Doyle wrote:
> > On Tue, 7 Sept 2021 at 03:45, Carlos O'Donell via Libc-alpha <
> > libc-alpha@sourceware.org> wrote:
> >
> >> diff --git a/localedata/locales/C b/localedata/locales/C
> >> new file mode 100644
> >> index 0000000000..ca801c79cf
> >> --- /dev/null
> >> +++ b/localedata/locales/C
> >
> >
> > [...]
> >
> >
> >>
> >>
> > +LC_TIME
> >> +% This is the POSIX Locale definition for the LC_TIME category with the
> >> +% exception that time is per ISO 8601 and 24-hour.
> >> +%
> >> +% Abbreviated weekday names (%a)
> >> +abday "Sun";"Mon";"Tue";"Wed";"Thu";"Fri";"Sat"
> >> +
> >> +% Full weekday names (%A)
> >> +day "Sunday";"Monday";"Tuesday";"Wednesday";"Thursday";/
> >> + "Friday";"Saturday"
> >> +
> >> +% Abbreviated month names (%b)
> >> +abmon "Jan";"Feb";"Mar";"Apr";"May";"Jun";"Jul";"Aug";"Sep";/
> >> + "Oct";"Nov";"Dec"
> >> +
> >> +% Full month names (%B)
> >> +mon "January";"February";"March";"April";"May";"June";"July";/
> >> + "August";"September";"October";"November";"December"
> >> +
> >> +% Week description, consists of three fields:
> >> +% 1. Number of days in a week.
> >> +% 2. Gregorian date that is a first weekday (19971130 for Sunday,
> >> 19971201 for Monday).
> >> +% 3. The weekday number to be contained in the first week of the year.
> >> +%
> >> +% ISO 8601 conforming applications should use the values 7, 19971201 (a
> >> +% Monday), and 4 (Thursday), respectively.
> >> +week 7;19971201;4
> >>
> >
> > It's obviously a bit late, but this is a difference from the
> Debian/Ubuntu
>
> It is never too late! Thank you for raising this.
>
No worries. Should have got to it sooner but well.
> Given that you've had problems with one application, other applications
> will have problems too.
>
> I think we should probably keep C == C.UTF-8 and not change any of the
> existing LC_TIME properties.
>
As far as I understand these issues (which is not very far) I think this
makes sense.
Cheers,
mwh
prev parent reply other threads:[~2022-01-30 23:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 15:43 [PATCH v12 0/2] C.UTF-8 Carlos O'Donell via Libc-alpha
2021-09-06 15:43 ` [PATCH v12 1/2] Add 'codepoint_collation' support for LC_COLLATE Carlos O'Donell via Libc-alpha
2021-09-06 17:20 ` Matheus Castanho via Libc-alpha
2021-09-06 17:28 ` Florian Weimer via Libc-alpha
2021-09-07 1:28 ` Carlos O'Donell via Libc-alpha
2021-09-07 1:57 ` Carlos O'Donell via Libc-alpha
2021-09-20 12:49 ` Matheus Castanho via Libc-alpha
2021-09-20 12:54 ` Carlos O'Donell via Libc-alpha
2021-09-06 15:43 ` [PATCH v12 2/2] Add generic C.UTF-8 locale (Bug 17318) Carlos O'Donell via Libc-alpha
2022-01-26 2:44 ` Michael Hudson-Doyle via Libc-alpha
2022-01-28 16:42 ` Carlos O'Donell via Libc-alpha
2022-01-30 23:58 ` Michael Hudson-Doyle via Libc-alpha [this message]
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ8wqtfnFF71bKhLVGe=g5fjWwGRTprGLQW-5tPCOyjJchHUaQ@mail.gmail.com' \
--to=libc-alpha@sourceware.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=michael.hudson@canonical.com \
/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: link
Be 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).