From: Zack Weinberg <zackw@panix.com>
To: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v11 1/5] Implement alternative month names (bug 10871).
Date: Thu, 11 Jan 2018 14:32:00 -0000 [thread overview]
Message-ID: <CAKCAbMhtAi-RDMegxDM0pTL7V8R94ek6NtFABxs8NiySg6Gqww@mail.gmail.com> (raw)
In-Reply-To: <20180111122535.GA13782@altlinux.org>
On Thu, Jan 11, 2018 at 7:25 AM, Dmitry V. Levin <ldv@altlinux.org> wrote:
> On Thu, Jan 11, 2018 at 12:46:06PM +0100, Rafal Luzynski wrote:
>> 11.01.2018 03:16 "Dmitry V. Levin" <ldv@altlinux.org> wrote:
>> > On Tue, Jan 09, 2018 at 12:59:21AM +0100, Rafal Luzynski wrote:
>> > > + /* Long month names, in the grammatical form used when the month
>> > > + forms part of a complete date. */
>> >
>> > ... when month name is a part of ...?
>>
>> Does the question mark mean that you are not sure? Well, this comment
>> has been provided by Zack Weinberg who is a native English speaker.
>
> I read this as "month is a part of a part of a complete date" which
> is too complex unless your intention is to highlight that month name
> is a subpart.
I did not mean this sentence to be a definitive native-speaker
pronouncement on How To Say This In English. That _anyone_ finds it
confusing is enough reason to revise it.
But I'm having trouble revising it - I'm sure it should begin with
/* Long month names, in the grammatical form used when ...
but I don't know what to put after "when" anymore. Perhaps the
problem is that I don't speak any language that needs this feature!
How would *you* describe it?
zw
next prev parent reply other threads:[~2018-01-11 14:32 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
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 [this message]
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=CAKCAbMhtAi-RDMegxDM0pTL7V8R94ek6NtFABxs8NiySg6Gqww@mail.gmail.com \
--to=zackw@panix.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).