Re: [RFC][PATCH v2 3/6] Implement the %OB specifier - alternative month names (bug 10871)

[Rafal Luzynski <digitalfreak at lingonborough dot com>]

4.11.2016 14:36 Florian Weimer <fweimer@redhat.com> wrote:
>
>
> On 03/29/2016 11:02 AM, Florian Weimer wrote:
> > On 03/25/2016 01:55 AM, Rafal Luzynski wrote:
> >
> >> 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.
> >
> > What's the status here on the POSIX side? It's marked as Accepted in
> > the tracker, but the changes apparently haven't been folded into
> > subsequent editions.
>
> This question has never been answered.

At least partial answer is here:
https://sourceware.org/ml/libc-alpha/2016-10/msg00319.html

> I think it's quite relevant to
> whether we can accept the patch or not.
>
> Florian

Please note that it's a bug that strftime() does not format the
month names in nominative/genitive case (more generally:
standalone/full date). Many other toolkits have the same bug
because they just call strftime() internally. And also it's been
accepted that it's a bug in POSIX that it does not specify %OB.

Is there any alternative solution for the bug?

Regards,

Rafal Luzynski