From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: libc-alpha@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v11 1/5] Implement alternative month names (bug 10871).
Date: Fri, 12 Jan 2018 03:44:00 -0000 [thread overview]
Message-ID: <1473144641.33095.1515728679368@poczta.nazwa.pl> (raw)
In-Reply-To: <b964827b-9017-2d72-8a26-249382bd42f5@redhat.com>
Thank you Carlos for your reviews. Please find my comments below:
11.01.2018 06:03 Carlos O'Donell <carlos@redhat.com> wrote:
>
> On 01/08/2018 03:59 PM, Rafal Luzynski wrote:
> > [...]
> > +#ifdef __USE_GNU
> > +# define ALTMON_1 __ALTMON_1
> > +# define ALTMON_2 __ALTMON_2
> > +# define ALTMON_3 __ALTMON_3
> > +# define ALTMON_4 __ALTMON_4
> > +# define ALTMON_5 __ALTMON_5
> > +# define ALTMON_6 __ALTMON_6
> > +# define ALTMON_7 __ALTMON_7
> > +# define ALTMON_8 __ALTMON_8
> > +# define ALTMON_9 __ALTMON_9
> > +# define ALTMON_10 __ALTMON_10
> > +# define ALTMON_11 __ALTMON_11
> > +# define ALTMON_12 __ALTMON_12
>
> OK. Requires _GNU_SOURCE, which is good because this is an extension not
> yet defined by POSIX.
I guess you meant __USE_GNU because that's what my patch uses. So does
/usr/include/langinfo.h everywhere. Should I use _GNU_SOURCE instead?
> > [...]
> > diff --git a/time/tst-strptime.c b/time/tst-strptime.c
> > index 34ad797..bbc1390 100644
> > --- a/time/tst-strptime.c
> > +++ b/time/tst-strptime.c
> > @@ -51,6 +51,12 @@ static const struct
> > 6, 0, 0, 1 },
> > { "ja_JP.EUC-JP", "2001 20 \xb7\xee", "%Y %U %a", 1, 140, 4, 21 },
> > { "ja_JP.EUC-JP", "2001 21 \xb7\xee", "%Y %W %a", 1, 140, 4, 21 },
> > + { "pl_PL.UTF-8", "21 lis 2017", "%d %b %Y", 2, 324, 10, 21 },
> > + { "pl_PL.UTF-8", "22 LIS 2017", "%d %B %Y", 3, 325, 10, 22 },
> > + /* TODO: Use the genitive case here as soon as it is added to localedata.
> > */
> > + { "pl_PL.UTF-8", "23 listopad 2017", "%d %B %Y", 4, 326, 10, 23 },
> > + /* The nominative case is incorrect here but it is parseable. */
> > + { "pl_PL.UTF-8", "24 listopad 2017", "%d %OB %Y", 5, 327, 10, 24 },
>
> Here we need examples of %OB for langauges that do *not* have genitive names
> in order to test the conversion of %OB for locales that would have this
> definition missing (tests that %OB does fall back to %B).
OK, I'm adding en_US.ISO-8859-1 for %B, de_DE.ISO-8859-1 for %b
(those locales look weird but they are already used in this file so
we don't need to add them), fr_FR.UTF-8 for %OB, and then I'll also
add es_ES.UTF-8 for %Ob in another patch which adds %Ob.
Regards,
Rafal
next prev parent reply other threads:[~2018-01-12 3:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 23:54 [PATCH v11 0/5][BZ 10871] Month names in alternative grammatical case Rafal Luzynski
2018-01-08 23:59 ` [PATCH v11 1/5] Implement alternative month names (bug 10871) Rafal Luzynski
2018-01-09 0:14 ` Rafal Luzynski
2018-01-11 4:20 ` Carlos O'Donell
2018-01-11 2:16 ` Dmitry V. Levin
2018-01-11 5:05 ` Carlos O'Donell
2018-01-12 3:44 ` Rafal Luzynski [this message]
2018-01-12 4:09 ` Carlos O'Donell
2018-01-11 11:46 ` Rafal Luzynski
2018-01-11 12:25 ` Dmitry V. Levin
2018-01-11 14:32 ` Zack Weinberg
2018-01-11 15:07 ` Dmitry V. Levin
2018-01-11 15:22 ` Zack Weinberg
2018-01-11 15:44 ` Rafal Luzynski
2018-01-11 22:26 ` Rafal Luzynski
2018-01-09 0:01 ` [PATCH v11 3/5] Abbreviated alternative month names (%Ob) also added " Rafal Luzynski
2018-01-11 5:05 ` Carlos O'Donell
2018-01-11 19:04 ` Rafal Luzynski
2018-01-11 19:14 ` Carlos O'Donell
2018-01-12 4:01 ` Rafal Luzynski
2018-01-09 0:03 ` [PATCH v11 5/5] Documentation to the above changes " Rafal Luzynski
2018-01-11 4:50 ` Carlos O'Donell
2018-01-12 4:21 ` Rafal Luzynski
2018-01-09 0:05 ` [PATCH] pl_PL: Add alternative month names " Rafal Luzynski
2018-01-09 0:20 ` Rafal Luzynski
2018-01-11 4:40 ` Carlos O'Donell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473144641.33095.1515728679368@poczta.nazwa.pl \
--to=digitalfreak@lingonborough.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).