From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v12 5/6] Documentation to the above changes (bug 10871).
Date: Thu, 25 Jan 2018 00:45:00 -0000 [thread overview]
Message-ID: <2074921143.499812.1516841147600@poczta.nazwa.pl> (raw)
In-Reply-To: <1090774665.1268651.1516745363342@poczta.nazwa.pl>
I have received a comment from Gnulib maintainers that this
documentation is too ambiguous because does not define which
date format should be considered "full" and which should be
considered "month standalone". I have explained that the date
is "full" if there is a day number and a month name (the week
day and the year number are optional) and the month name is
"standalone" when there is no day number (it may be just the
month name alone, or if a year number is added this still counts
as standalone). It has been requested to add this definition
to the glibc documentation.
But, OTOH, I can't guarantee this works the same in all languages
which have this issue. Maybe we should add a phrase "in many
languages" or "in most of the languages which need this feature"?
Any suggestions how to fix the documentation? Does anybody want
to commit immediately?
Regards,
Rafal
next prev parent reply other threads:[~2018-01-25 0:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 8:12 [PATCH v12 0/6][BZ 10871] Month names in alternative grammatical case Rafal Luzynski
2018-01-12 8:14 ` [PATCH v12 1/6] Implement alternative month names (bug 10871) Rafal Luzynski
2018-01-22 10:36 ` [COMMITTED][PATCH " Rafal Luzynski
2018-01-22 15:51 ` Joseph Myers
2018-01-22 20:15 ` Rafal Luzynski
2018-01-12 8:16 ` [PATCH v12 3/6] Abbreviated alternative month names (%Ob) also added " Rafal Luzynski
2018-01-22 10:38 ` [COMMITTED][PATCH " Rafal Luzynski
2018-01-12 8:18 ` [PATCH v12 5/6] Documentation to the above changes " Rafal Luzynski
2018-01-15 3:42 ` Rical Jasan
2018-01-15 6:28 ` Carlos O'Donell
2018-01-15 8:31 ` Rical Jasan
2018-01-15 11:53 ` Rafal Luzynski
2018-01-15 11:47 ` Rafal Luzynski
2018-01-18 12:04 ` [PING][PATCH " Rafal Luzynski
2018-01-18 13:36 ` Joseph Myers
2018-01-20 8:44 ` Carlos O'Donell
2018-01-22 16:01 ` Joseph Myers
2018-01-20 8:36 ` [PATCH " Rical Jasan
2018-01-20 8:39 ` Carlos O'Donell
2018-01-20 10:50 ` Rafal Luzynski
2018-01-22 8:43 ` Rafal Luzynski
2018-01-23 3:41 ` Rical Jasan
2018-01-23 22:09 ` Rafal Luzynski
2018-01-25 0:45 ` Rafal Luzynski [this message]
2018-01-25 1:47 ` Carlos O'Donell
2018-01-31 17:22 ` Rafal Luzynski
2018-01-22 10:40 ` Rafal Luzynski
2018-01-12 8:20 ` [PATCH v12 6/6] pl_PL: Add alternative month names " Rafal Luzynski
2018-01-22 10:42 ` [COMMITTED][PATCH " Rafal Luzynski
2018-01-13 11:05 ` [PATCH v12 0/6][BZ 10871] Month names in alternative grammatical case Rafal Luzynski
2018-01-14 3:53 ` Carlos O'Donell
2018-01-14 15:03 ` Rafal Luzynski
2018-01-20 8:41 ` Carlos O'Donell
2018-01-20 10:47 ` Rafal Luzynski
2018-01-20 22:46 ` Carlos O'Donell
2018-02-19 10:12 ` Khem Raj
2018-02-22 0:24 ` Rafal Luzynski
2018-02-22 5:25 ` Carlos O'Donell
2018-02-22 5:58 ` Khem Raj
2018-02-22 6:52 ` 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=2074921143.499812.1516841147600@poczta.nazwa.pl \
--to=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).