From: Carlos O'Donell <carlos@redhat.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>,
libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH v2 3/6] Implement the %OB specifier - alternative month names (bug 10871)
Date: Tue, 29 Mar 2016 14:15:00 -0000 [thread overview]
Message-ID: <56FA8E03.2020102@redhat.com> (raw)
In-Reply-To: <1155243857.420233.60a90901-4334-4cea-aa99-f76884316a10.open-xchange@poczta.nazwa.pl>
On 03/24/2016 08:55 PM, Rafal Luzynski wrote:
> Some languages (Slavic, Baltic, etc.) require a genitive case of the
> month name when formatting a full date (with the day number) while
> they require a nominative case when referring to the month standalone.
>
> strftime() now implements a %OB format specifier which generates an
> alternative month name. For the languages which require both nominative
> and genitive case of the month names it is expected that it outputs
> the alternative month name which should be a nominative (sic!) case
> or whatever is appropriate when formatting the month names standalone
> (without a day). For those languages %B will return the basic month
> name but from now it is expected to be a genitive case or whatever is
> appropriate when formatting full dates (including both day and month).
> This means that all applications using %B to retrieve the month
> name standalone should use %OB from now. For those languages which
> do not use different (nominative and genitive) cases of the month
> name or do not yet have their locales updated %OB will retrieve
> the same string as %B so moving to %OB will be harmless as long
> as the version of glibc which supports this feature is used.
>
> strptime() now accepts both nominative and genitive month names.
Please make sure you read through the "Contribution Checklist"
https://sourceware.org/glibc/wiki/Contribution%20checklist
Do you have copyright assignment with the FSF for glibc?
Your change is more than the accepted 11 lines and thus
legally significant and requiring copyright assignment.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2016-03-29 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 0:55 Rafal Luzynski
2016-03-29 9:02 ` Florian Weimer
2016-03-29 10:59 ` keld
2016-11-04 13:36 ` Florian Weimer
2016-11-05 10:42 ` Rafal Luzynski
2016-03-29 14:15 ` Carlos O'Donell [this message]
2016-03-29 23:23 ` Rafal Luzynski
2016-03-29 14:31 ` Dmitry V. Levin
2016-03-29 23:31 ` Rafal Luzynski
2016-06-01 10:42 ` Dmitry V. Levin
2016-06-01 21:51 ` Rafal Luzynski
2016-06-01 22:20 ` Paul Eggert
2016-06-01 23:54 ` Rafal Luzynski
2016-06-02 7:03 ` Paul Eggert
2016-06-03 7:08 ` Rafal Luzynski
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=56FA8E03.2020102@redhat.com \
--to=carlos@redhat.com \
--cc=digitalfreak@lingonborough.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).