From: Chris Leonard <cjlhomeaddress@gmail.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [RFC][PATCH v2 1/6] Implement alternative month names (bug 10871).
Date: Sat, 26 Mar 2016 00:58:00 -0000 [thread overview]
Message-ID: <CAHdAatYq9VkoS6RaNvoi9BfGL=sGFvyYHke+dEDJA-x=4yRi3w@mail.gmail.com> (raw)
In-Reply-To: <143256632.450925.970c398f-fa88-4e8c-b1c0-1869f0cf78de.open-xchange@poczta.nazwa.pl>
On Fri, Mar 25, 2016 at 4:55 PM, Rafal Luzynski
<digitalfreak@lingonborough.com> wrote:
>> 25.03.2016 02:54 Chris Leonard <cjlhomeaddress@gmail.com> wrote:
> Does glibc have any support for the lunar calendars? Looks like
> it does not at all. Although probably it would be good idea for those
> countries/locales which use such calendars.
I have to admit I have never looked into it at the code level. I am
probably mistaken in making an assumption of such support from reading
the "mon" description in TR 14652.
TR 14652
http://www.open-std.org/JTC1/SC22/WG20/docs/n972-14652ft.pdf
states:
mon
Define the full month names, to be referenced by the %B field
descriptor. The operand consists of twelve or thirteen semicolon-
separated strings. The first string is the full name of the first month
of the year (January), the second the full name of the second month,
and so on.
I have not had occasion to create a locale with 13 months (yet), but I
had thought it would be supported, my bad.
cjl
next prev parent reply other threads:[~2016-03-26 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 0:52 Rafal Luzynski
2016-03-25 1:55 ` Chris Leonard
2016-03-25 20:55 ` Rafal Luzynski
2016-03-26 0:58 ` Chris Leonard [this message]
2016-03-29 23:16 ` 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='CAHdAatYq9VkoS6RaNvoi9BfGL=sGFvyYHke+dEDJA-x=4yRi3w@mail.gmail.com' \
--to=cjlhomeaddress@gmail.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).